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

[Brian Murray]

On Sat, Dec 08, 2018 at 07:38:38PM -0000, Christophe R. Patraldo wrote:
> This still isn't working right, at least not for me. I'm trying to
> upgrade the release from 16.04 to 18.04 installed on Google Compute
> Engine. Is it a different bug or am I missing something?

The fixed version of screen is in the -updates pocket for Ubuntu 18.04.
Do you have -updates enabled for Ubuntu 16.04?

--
Brian Murray

-- 
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:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in screen source package in Bionic:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid

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