Hi there, I just got hit by the same bug upon a reboot after 486 days of uptime...
NB, this system booted for the first time with systemd after having
being upgraded from 9.12 to 10.3 on 2020-03-25 following the Debian
Release Notes!
On Fri, 24 May 2019 00:43:25 +0200, Axel Beckert wrote:
> Phil Dibowitz wrote:
> > Tried several reboots, it's very reproducible.
>
> Thanks.
Same here.
> > I tried adding the '-' and also tried moving the file to /usr/lib,
> > either way nothing works.
>
> Strange.
FWIW, I have two copies of the tmpfiles.d:
```
root@baloo:~# diff -u /etc/tmpfiles.d/screen-cleanup.conf
/usr/lib/tmpfiles.d/screen-cleanup.conf
--- /etc/tmpfiles.d/screen-cleanup.conf 2020-03-25 23:15:35.132326571
+0100
+++ /usr/lib/tmpfiles.d/screen-cleanup.conf 2021-02-20
21:36:23.000000000 +0100
@@ -1 +1 @@
-d /run/screen 1777 root utmp
+d /run/screen 0777 root utmp
root@baloo:~# dpkg-query -S /etc/tmpfiles.d/screen-cleanup.conf
dpkg-query: no path found matching pattern /etc/tmpfiles.d/screen-cleanup.conf
root@baloo:~#
```
I am almost sure I have not manually created such a file, also
considering the following:
```
root@baloo:~# dpkg-query -W screen
screen 4.6.2-3+deb10u1
root@baloo:~# dpkg-statoverride --list | grep screen
root@baloo:~# ls -l $(command -v screen)
-rwxr-xr-x 1 root root 470024 Feb 20 21:59 /usr/bin/scree
root@baloo:~#
```
And indeed the file has been recorded as "automatically installed"
during the stretch => buster upgrade following the Release Notes:
```
root@baloo:/etc# git log --raw tmpfiles.d/screen-cleanup.conf
commit 9078ca27a81123f0467023e2d0869e32a646cdeb
Author: root <r...@baloo.pca.it>
Date: Wed Mar 25 23:26:50 2020 +0100
committing changes in /etc made by "apt full-upgrade"
Package changes:
-abcde 2.8.1-1 all
+abcde 2.9.3-1 all
-alsa-utils 1.1.3-1 amd64
-apache2 2.4.25-3+deb9u9 amd64
-apache2-bin 2.4.25-3+deb9u9 amd64
-apache2-data 2.4.25-3+deb9u9 all
-apache2-utils 2.4.25-3+deb9u9 amd64
-apt 1.4.9 amd64
-apt-listchanges 3.10 all
-apt-utils 1.4.9 amd64
-at 3.1.20-3 amd64
+alsa-utils 1.1.8-2 amd64
+apache2 2.4.38-3+deb10u3 amd64
+apache2-bin 2.4.38-3+deb10u3 amd64
+apache2-data 2.4.38-3+deb10u3 all
+apache2-utils 2.4.38-3+deb10u3 amd64
+apt 1.8.2 amd64
+apt-listchanges 3.19 all
+apt-utils 1.8.2 amd64
+at 3.1.23-1 amd64
-avahi-utils 0.6.32-2 amd64
+avahi-utils 0.7-4+b1 amd64
-bash 4.4-5 amd64
+bash 5.0-4 amd64
-bc 1.06.95-9+b3 amd64
[...]
-schroot-common 1.6.10-3+deb9u1 all
-screen 4.5.0-6 amd64
+scdaemon 2.2.19-2~bpo10+1 amd64
+schroot 1.6.10-6+b1 amd64
+schroot-common 1.6.10-6 all
+screen 4.6.2-3 amd64
-smbclient 2:4.5.16+dfsg-1+deb9u2 amd64
[...]
+w3m 0.5.3-37 amd64
-wget 1.18-5+deb9u3 amd64
+wget 1.20.1-1.1 amd64
:000000 100644 0000000 eb1b9f8 A tmpfiles.d/screen-cleanup.conf
root@baloo:/etc# git reflog
[...]
6b30163 HEAD@{77}: commit: committing changes in /etc made by "apt-get
autoremove --purge"
9078ca2 HEAD@{78}: commit: committing changes in /etc made by "apt full-upgrade"
9c12e60 HEAD@{79}: commit: committing changes in /etc made by "apt-get upgrade"
aa69b01 HEAD@{80}: commit: apt/sources.list.d/ftp.ch.debian.org.list:
s/stretch/buster/g
[...]
root@baloo:/etc#
```
FWIW, the "null" systemd service is there, as per postinst[1]:
```
root@baloo:~# systemctl status screen-cleanup.service
● screen-cleanup.service
Loaded: masked (Reason: Unit screen-cleanup.service is masked.)
Active: inactive (dead)
root@baloo:~#
root@baloo:~# cat /lib/systemd/system/screen-cleanup.service
root@baloo:~# ls -l /lib/systemd/system/screen-cleanup.service
lrwxrwxrwx 1 root root 9 Aug 30 2018
/lib/systemd/system/screen-cleanup.service -> /dev/null
root@baloo:~# dpkg-query -S /lib/systemd/system/screen-cleanup.service
dpkg-query: no path found matching pattern
/lib/systemd/system/screen-cleanup.service
root@baloo:~#
```
[1] <https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1462692>
> > I tried running `systemd-tmpfiles --create --remove --boot
> > --exclude-prefix=/dev`, but it doesn't create /run/screen at all. No
> > matter how I ran it, I could not get it to create that directory.
>
> Very strange. *frowning*
In my case the problem had nothing to do with screen, but instead with
an incorrect ownership of / (for a reason I still could not find out...)
and systemd-tmpfiles complaining, but the service not exiting with
errors, instead showing a useless message (thanks to the Internet for
the solution[2]):
```
root@baloo:~# systemctl status systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static;
vendor preset: enabled)
Active: active (exited) since Sun 2021-07-25 14:21:56 CEST; 1min 5s ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 749 ExecStart=/bin/systemd-tmpfiles --create --remove --boot
--exclude-prefix=/dev (code=exited, status=73)
Main PID: 749 (code=exited, status=73)
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /tmp during canonicalization of /tmp.
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /tmp during canonicalization of /tmp.
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /tmp during canonicalization of /tmp.
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /tmp during canonicalization of /tmp.
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /tmp during canonicalization of /tmp.
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /run during canonicalization of /run/log/journal.
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /run during canonicalization of /run/log/journal/5b4e160048712cf097f2bed553cbf
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /run during canonicalization of /run/log/journal/5b4e160048712cf097f2bed553cbf
Jul 25 14:21:56 baloo systemd-tmpfiles[749]: Detected unsafe path transition /
→ /run during canonicalization of /run/log/journal/5b4e160048712cf097f2bed553cbf
Jul 25 14:21:56 baloo systemd[1]: Started Create Volatile Files and Directories.
root@baloo:~# systemd-tmpfiles --create /etc/tmpfiles.d/screen-cleanup.conf
Detected unsafe path transition / → /run during canonicalization of /run.
root@baloo:~# echo $?
73
root@baloo:~# ls -l /run/*screen*
ls: cannot access '/run/*screen*': No such file or directory
root@baloo:~# ls -l /
total 98
drwxr-xr-x 2 root root 4096 Jul 25 12:45 bin
drwxr-xr-x 6 root root 2048 Jul 25 12:46 boot
drwxr-xr-x 19 root root 3860 Jul 25 14:22 dev
drwxr-xr-x 3 root root 4096 Oct 8 2019 efi
drwxr-xr-x 133 root root 12288 Jul 25 12:47 etc
drwxr-xr-x 5 root root 4096 Dec 8 2019 home
lrwxrwxrwx 1 root root 36 Jun 20 20:29 initrd.img ->
boot/initrd.img-5.10.0-0.bpo.7-amd64
lrwxrwxrwx 1 root root 35 Jul 24 10:23 initrd.img.old ->
boot/initrd.img-5.4.0-0.bpo.4-amd64
drwxr-xr-x 18 root root 4096 Jun 20 20:26 lib
drwxr-xr-x 2 root root 4096 Mar 25 2020 lib64
drwx------ 2 root root 16384 Mar 25 2013 lost+found
drwxr-xr-x 4 root root 4096 Mar 26 2013 media
drwxr-xr-x 2 root root 4096 Oct 26 2017 mnt
drwxr-xr-x 2 nobody nogroup 4096 May 9 2013 nonexistent
drwxr-xr-x 2 root root 4096 Mar 25 2013 opt
dr-xr-xr-x 279 root root 0 Jul 25 14:21 proc
drwx------ 20 root root 4096 Jul 25 14:26 root
drwxr-xr-x 34 root root 1060 Jul 25 14:22 run
drwxr-xr-x 2 root root 12288 Jul 25 12:45 sbin
drwxr-xr-x 14 root root 4096 Jun 28 22:43 srv
dr-xr-xr-x 13 root root 0 Jul 25 14:21 sys
drwxrwxrwt 7 root root 4096 Jul 25 14:28 tmp
drwxr-xr-x 10 root root 4096 Mar 25 2013 usr
drwxr-xr-x 12 root root 4096 Jan 21 2018 var
lrwxrwxrwx 1 root root 33 Jun 20 20:29 vmlinuz ->
boot/vmlinuz-5.10.0-0.bpo.7-amd64
lrwxrwxrwx 1 root root 32 Jul 24 10:23 vmlinuz.old ->
boot/vmlinuz-5.4.0-0.bpo.4-amd64
root@baloo:~# ls -ld /
drwxr-xr-x 24 luca.capello pca 4096 Jul 25 12:54 /
root@baloo:~# chown root:root /
root@baloo:~# ls -ld /
drwxr-xr-x 24 root root 4096 Jul 25 12:54 /
root@baloo:~# systemd-tmpfiles --create /etc/tmpfiles.d/screen-cleanup.conf
root@baloo:~# ls -l /run/*screen*
total 0
root@baloo:~# ls -ld /run/*screen*
drwxrwxrwt 2 root utmp 40 Jul 25 14:33 /run/screen
root@baloo:~#
```
[2]
<https://discourse.nixos.org/t/tons-of-detected-unsafe-path-transititions-after-migrating-install-to-new-hd/8782>
Thx, bye,
Gismo / Luca
-- System Information:
Debian Release: 10.10
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-0.bpo.7-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages screen depends on:
ii libc6 2.28-10
ii libpam0g 1.3.1-5
ii libtinfo6 6.1+20181013-2+deb10u2
ii libutempter0 1.1.6-3
screen recommends no packages.
Versions of packages screen suggests:
pn byobu | screenie | iselect <none>
ii ncurses-term 6.1+20181013-2+deb10u2
-- no debconf information
signature.asc
Description: PGP signature
