Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#72793 - screen-4.8.0-3 wrong perms on /run/screens
Attached to Project:
Arch Linux
Opened by Gaetan Bisson (vesath) - Friday, 19 November 2021, 23:20 GMT
Last edited by Antonio Rojas (arojas) - Friday, 19 November 2021, 23:26 GMT
Opened by Gaetan Bisson (vesath) - Friday, 19 November 2021, 23:20 GMT
Last edited by Antonio Rojas (arojas) - Friday, 19 November 2021, 23:26 GMT
|
Detailsscreen-4.8.0-3 ships with /usr/lib/tmpfiles.d/screen.conf which contains:
d /run/screens 0755 root root - But then calling `screen` yields: Directory '/run/screens' must have mode 777. (Which is a critical error: no screen can be created.) |
This task depends upon
Comment by Gaetan Bisson (vesath) -
Friday, 19 November 2021, 23:23 GMT
That of course doesn't happen when /usr/bin/screen is setuid. My binary lost its setuid bit and that's what broke my system. Apologies. This report can be ignored.