[Bug 272042] Directory 1002/ is sometimes missing from /var/run/user/

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 18 Jun 2023 09:28:10 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272042

--- Comment #4 from Graham Perrin <grahamperrin@freebsd.org> ---
Created attachment 242861
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242861&action=edit
messages from today's boot

From <https://markmail.org/message/pikg6ra5cq52pecw>: 

> % ls -hln /etc/pam.d/system
> -rw-r--r--  1 0  0   540B  7 Oct  2022 /etc/pam.d/system
> % 

All files in that directory were created more than four years ago (2018-12-13). 

/etc/pam.d/system is one of five files that were modified at the same time last
year: 

% ls -hlnrt /etc/pam.d | grep 2022
-rw-r--r--  1 0  0   498B  7 Oct  2022 other
-rw-r--r--  1 0  0   576B  7 Oct  2022 sshd
-rw-r--r--  1 0  0   540B  7 Oct  2022 system
-rw-r--r--  2 0  0   359B  7 Oct  2022 ftpd
-rw-r--r--  2 0  0   359B  7 Oct  2022 ftp
% 


<https://markmail.org/message/pikg6ra5cq52pecw> also included output from 
uname -aKU

FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #6
main-n263493-4e8d558c9d1c-dirty: Sun Jun 11 06:22:01 BST 2023    
grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
amd64 1400090 1400090


Towards diagnosis
=================

With no recent change to /etc/pam.d/system, what might explain the recent
randomness – the occasional non-creation of my /var/run/user/1002 directory? 


If it helps (beginning to give more thought to the background): 

* Login Screen (SDDM) behaviour is to 
  automatically log in grahamperrin with session Plasma (X11)

* my everyday use of CURRENT is very rarely GENERIC, 
  nearly always GENERIC-NODEBUG

* ZFS-related bug 271772 comment 17 reminds me that I began testing with 
  GENERIC on 2023-06-11

* my first email about the absence of /var/run/user/1002 was later that day.

Now, I wonder whether the trigger for this bug: 

* has existed for (much) longer than a week

* was, somehow, previously suppressed by GENERIC-DEBUG.

----

From today's boot (see attachment), is the message below directly relevant?

Jun 18 09:08:34 mowa219-gjp4-8570p-freebsd dbus-daemon[2486]: [system] Rejected
send message, 2 matched rules; type="method_call", sender=":1.7" (uid=1002
pid=3369 comm="/usr/local/lib/libexec/org_kde_powerdevil")
interface="org.freedesktop.ConsoleKit.Manager" member="CanSuspendThenHibernate"
error name="(unset)" requested_reply="0"
destination="org.freedesktop.ConsoleKit" (uid=0 pid=3316
comm="/usr/local/sbin/console-kit-daemon --no-daemon")


----

This morning's packages were installed to a new boot environment
(n263493-4e8d558c9d1c-c) that is activated but not yet booted. 

I'll boot in a few minutes … GENERIC-NODEBUG instead of GENERIC …

-- 
You are receiving this mail because:
You are the assignee for the bug.