> * Are "/run" and "/var/run" the same directory? (They should be, > otherwise _that_ is the bug.)
They are: [phil@rider ~]$ ls -dli /run /var/run 9766 drwxr-xr-x 34 root root 1220 May 23 06:35 /run 131075 lrwxrwxrwx 1 root root 4 Jun 25 2011 /var/run -> /run > * What are the permissions of the directory "/run"? See above. > * What are the permissions of /usr/bin/screen? (i.e. are there any > stat-overrides for screen?) [phil@rider ~]$ ls -l /usr/bin/screen -rwxr-xr-x 1 root root 465928 Jul 15 2018 /usr/bin/screen > * Does /etc/tmpfiles.d/screen-cleanup.conf exist? [phil@rider ~]$ cat /etc/tmpfiles.d/screen-cleanup.conf d /run/screen 1777 root utmp > * Does /lib/systemd/system/screen-cleanup.service exist and is it a > symbolic link to /dev/null? (Just to make sure systemd does not run > the according init script, see > https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1462692) [phil@rider ~]$ ls -l /lib/systemd/system/screen-cleanup.service lrwxrwxrwx 1 root root 9 Jun 18 2015 /lib/systemd/system/screen-cleanup.service -> /dev/null > All these questions can be easily answered with sending the output of > these two commands to this bug report: Heh. I got it. > * How quickly after the reboot did this happen? Given the prompt, I > assume it wasn't started from a cron-job with "@reboot" or such. I had logged into fluxbox via xdm, so... shortly, but definitely not THAT quickly. :) > So I assume that this issue is not related to any of these issues, > despite looking very similar. Don't think so... -- Phil Dibowitz [email protected] Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." - Dr. Seuss
signature.asc
Description: OpenPGP digital signature
