** Changed in: screen (Debian)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871879
Title:
After upgrading /var/run/screen lacks right permissions
To manag
** Changed in: screen (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871879
Title:
After upgrading /var/run/screen lacks right permissions
To manage
Seems fixed now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871879
Title:
After upgrading /var/run/screen lacks right permissions
To manage notifications about this bug go to:
https://bugs.launch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: screen (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871879
Title:
Afte
Must take my own comment #9 down: this is there again: upgrading from
Ubuntu 10.04.4 to Ubuntu 12.04.1 using byobu for login leads to message:
"/var/run/screen must have permission 0777". After rebooting.
changing /var/run/screen once to permissions 0777 fixes this. The change
seems to be persiste
Upgrading to precise solves this bug. The newer install script seems
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871879
Title:
After upgrading /var/run/screen lacks right permissions
To ma
The bug is again there:
Upgrade from Ubuntu 11.10 to 12.04 ...
After it is ready login:
> Directory '/var/run/screen' must have mode 777.
> Directory '/var/run/screen' must have mode 777.
> Directory '/var/run/screen' must have mode 777.
---
Versions:
ii byobu5.6-0
I could make the bug vanish by removing screen, purging all configuration
files, searching for not removed files, deleting them by hand, removing all
statoverrides, then reinstalling screen.
Looks a lot like something left over from an older version of screen playing
with newer versions breaking
On a new install it is working. On an old, upgraded system it is not (after
upgrading).
I had to add an dpkg-statoverride to get rid of the error. On none of the
systems affected there was a statoverride given for "/var/run/screen". No
startup files where modified.
--
You received this bug not
** Changed in: screen (Debian)
Status: Unknown => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871879
Title:
After upgrading /var/run/screen lacks right permissions
To manage not
Hmm, I've tried to reproduce this bug, and I'm not able to.
I am able to login and automatically launch screen+byobu in Ubuntu
11.10, with my /var/run/screen/ directory permissions in the system
default:
drwxrwxr-x 3 root utmp 60 2011-10-10 12:53 /var/run/screen/
and the system defaul
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871879
Title:
After upgrading /var/run/screen lacks right permissions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
Hi Thomas,
> Since this bug is now known for about one year, could you please fix
it?
Just because a bug is known for a while does not mean, it's trivially to
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
This is possibly related to
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/727741
** Bug watch added: Debian Bug tracker #471763
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471763
** Also affects: screen (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471763
Imp
The permissions shall better be set to 01777 on /var/run/screen.
Allowing only the creator to remove the socket created per screen
session. Otherwise it's quite easy to execute a denial of service attack
localy: erase all sockets ...
--
You received this bug notification because you are a member
15 matches
Mail list logo
