[Bug 1761997] Re: /var/run needs mode 777 in bionic

[Axel Beckert]

Hi,

Brian Murray wrote:
> Ah I think it (the tmpfile isn't created) because /usr/bin/screen is
> 2755 in Ubuntu 16.04 but 755 in Ubuntu 18.04. Here's the change between
> the two releases.

Ah! That's due to switching to use libutempter. We're getting quite
close to the issue.

I though wonder how to fix that for Bionic in the best way. Maybe
adding something like this to screen.preinst (not postinst):

perms="`stat -c%a /usr/bin/screen`"
override=/etc/tmpfiles.d/screen-cleanup.conf
if [ $perms -eq 2755 ]; then
    chmod 0777 /var/run/screen
[ -f $override ] || echo 'd /var/run/screen 0777 root utmp' > $override

I assume that this is nothing which would make sense to add to future
releases of Debian's screen package, or does it?

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1761997

Title:
  /var/run needs mode 777 in bionic

Status in screen package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  [Test Case]
  1) have an Ubuntu 16.04
  2) rm /etc/cron.daily/mlocate (this'll ensure you get a conffile prompt)
  3) ssh to Ubuntu 16.04 system so the release upgrade is run in screen
  4) run do-release-upgrade -d
  5) wait for the conffile prompt from mlocate
  6) ssh to the Ubuntu 16.04 system being upgraded
  7) sudo -i
  8) run screen -rd

  With the version of screen in the release pocket you'll receive the
  following error:

  root at clean-xenial-amd64:~# screen -rd
  Directory '/run/screen' must have mode 777.

  [Original Description]
  I saw some odd behaviour of screen during the upgrade from Xenial to Bionic using do-release-upgrade. I was trying to use screen to reattach to an upgrade process that had gone sideways during a router daemon upgrade (duh). But I was told that the permissions on /run/screen needed to be 777. Does the bionic version of screen have that as a requirement? And if so, perhaps do-release-upgrade should set those permissions in anticipation of the upgrade process so that screen works with both old and new versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1761997/+subscriptions