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
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?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
$ sudo do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,263 kB]
Fetched 1,264 kB in 0s (0 B/s)
authenticate 'bionic.tar.gz' aga
Thanks to Brian for his patience with the remote debugging session via
Launchpad comments. And for the resulting HOWTO for reproducing the
issue. :-)
Given that Stretch's screen package is without libutempter, too, this
might bite Debian with Stretch to Buster upgrades inside screen, too.
I'm thou
\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 b
This bug was fixed in the package screen - 4.6.2-1ubuntu1
---
screen (4.6.2-1ubuntu1) bionic; urgency=medium
* debian/screen.preinst: When screen is unpacked but not configured the
permissions for /var/run/screen need to be changed so that an existing
screen session can be r
I went ahead and verified this by ssh'ing to an Ubuntu 16.04, starting
the upgrade after having modified /etc/cron.daily/mlocate and changing
DistUpgradeController.py so -proposed would not be disabled. During the
upgrade process screen was unpacked, then I received the mlocate conf
file prompt bef
Hello Mark, or anyone else affected,
Accepted screen into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/screen/4.6.2-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
** Changed in: screen (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: screen (Ubuntu)
Status: Triaged => In Progress
** Also affects: screen (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Bion
Axel (sorry about that),
I was confused about what order (installing the new binary vs running
the preinst) things happened in. Checking the perms for 2755 in the
preinst does work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
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 be
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.
(xenial-amd64)root@impulse:/mnt/sec-machines# dpkg --unpack
screen_4.6.2-1_amd64.deb
(Reading database ... 23570 files and directories c
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
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.
override_dh_auto_install:
- # can't call the normal install target b/c it installs the info files
- # and other crud
- $
/etc/tmpfiles.d/screen-cleanup.conf does not exist on an Ubuntu 16.04
install nor is it created when I install screen on a Ubuntu 16.04
system.
$ schroot -u root -c xenial-amd64
(xenial-amd64)root@impulse:/mnt/sec-machines# apt-get install screen
Reading package lists... Done
Building dependency
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 change
/run/screen has the following permissions
drwxrwxr-x 3 root utmp60 Jul 19 06:06 screen
screen-cleanup is a masked service in response to bug 1462692, so the
permissions of /run/screen are never changed in Ubuntu 16.04.
bdmurray@clean-xenial-amd64:~$ sudo service screen-cleanup status
[sudo
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 syst
One could also follow these simple steps to recreate the bug.
1) Start screen on Ubuntu 16.04
2) Download bionic's screen
3) Run 'sudo dpkg --unpack screen_4.6.2-1_amd64.deb'
4) try to reattach to screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** 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 /ru
** Tags added: id-5b05e6a18adf2325732c69ca
--
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.
** Tags added: id-5ad8bd0d1f6a45cc0c62874b
--
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.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Milestone: None => ubuntu-18.04.1
** Changed in: screen (Ubuntu)
Milestone: None => ubuntu-18.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
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 manag
** Changed in: screen (Ubuntu)
Status: Invalid => Triaged
--
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 bu
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 clob
I've been able to recreate this during a distribution upgrade from 16.04
to 18.04 (directory permissions switched from 775 to 777) when the
package is unpacked but not yet configured. This could end up causing an
issue at a conffile prompt for a different package if your screen
session (which the r
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 clobbers them
> again.
I currently don't see that clobbering, at least no
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 clobbers them
again.
** Package changed: ubuntu-release-upgrader (Ubuntu) => screen (Ubuntu)
** Chan
29 matches
Mail list logo
