On Sat, Dec 08, 2018 at 07:38:38PM -, 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
\o/ thanks all, glad that one got in for the point release.
Mark
--
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
Hi Brian,
Brian Murray wrote:
> Alex - I don't think that will work because when the new version of
> screen is unpacked the permissions are 755, so the check would need to
> be for 755, not 2755.
No. I said into _pre_inst, not postinst, so that everything is in
place and fixed when screen has
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
Hi Brian,
Brian Murray wrote:
> /run/screen has the following permissions
>
> drwxrwxr-x 3 root utmp60 Jul 19 06:06 screen
Thanks. This is indeed not the expected setting.
> screen-cleanup is a masked service in response to bug 1462692, so the
> permissions of /run/screen are never
Hi Brian,
Brian Murray wrote:
> + 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
On Wed, Apr 11, 2018 at 10:21:20AM -, Axel Beckert wrote:
> Steve Langasek wrote:
> > I believe this is a bug in screen. The postinst script has code to
> > handle the changed requirements for /run/screen permissions, but then
> > immediately afterwards a debhelper code snippet runs which
