** Description changed:

- 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.
+ [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@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.

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

Title:
  /var/run needs mode 777 in bionic

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to