Date: Sun, 18 Jun 2023 09:28:10 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 272042] Directory 1002/ is sometimes missing from /var/run/user/ Message-ID: <bug-272042-7788-D8YBiOFovw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272042-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-272042-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272042 --- Comment #4 from Graham Perrin <grahamperrin@freebsd.org> --- Created attachment 242861 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D242861&action= =3Dedit messages from today's boot >From <https://markmail.org/message/pikg6ra5cq52pecw>:=20 > % ls -hln /etc/pam.d/system > -rw-r--r-- 1 0 0 540B 7 Oct 2022 /etc/pam.d/system > %=20 All files in that directory were created more than four years ago (2018-12-= 13).=20 /etc/pam.d/system is one of five files that were modified at the same time = last year:=20 % 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 %=20 <https://markmail.org/message/pikg6ra5cq52pecw>; also included output from=20 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=20=20=20=20 grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GE= NERIC amd64 1400090 1400090 Towards diagnosis =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D With no recent change to /etc/pam.d/system, what might explain the recent randomness =E2=80=93 the occasional non-creation of my /var/run/user/1002 d= irectory?=20 If it helps (beginning to give more thought to the background):=20 * Login Screen (SDDM) behaviour is to=20 automatically log in grahamperrin with session Plasma (X11) * my everyday use of CURRENT is very rarely GENERIC,=20 nearly always GENERIC-NODEBUG * ZFS-related bug 271772 comment 17 reminds me that I began testing with=20 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:=20 * 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] Reje= cted send message, 2 matched rules; type=3D"method_call", sender=3D":1.7" (uid= =3D1002 pid=3D3369 comm=3D"/usr/local/lib/libexec/org_kde_powerdevil") interface=3D"org.freedesktop.ConsoleKit.Manager" member=3D"CanSuspendThenHi= bernate" error name=3D"(unset)" requested_reply=3D"0" destination=3D"org.freedesktop.ConsoleKit" (uid=3D0 pid=3D3316 comm=3D"/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.=20 I'll boot in a few minutes =E2=80=A6 GENERIC-NODEBUG instead of GENERIC =E2= =80=A6 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272042-7788-D8YBiOFovw>