Looks similar to the also exhaustly discussed http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=471763
** Bug watch added: Debian Bug tracker #471763
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471763
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The last commenter is seeing Bug #574773.
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
(on Lucic)
screen
Cannot make directory '/var/run/screen': Permission denied
ls -l /etc/rc*/*screen-cleanup*
lrwxrwxrwx 1 root root 24 2009-07-21 03:50 /etc/rcS.d/S70screen-cleanup -
../init.d/screen-cleanup
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this
Please provide the output of:
$ ls -l /etc/rc*/*screen-cleanup*
There should be a link present (via /etc/rcS.d/S70screen-cleanup in my
case).
In case it is, something breaks this later again on startup.
What is the error when you want to start screen? The Cannot make
directory
Yeah, bug is back in Lucid. I just encountered it on a clean install.
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
i got the same problem on lucid (10.4)... :-(
'sudo /etc/init.d/screen-cleanup start' helped. thank you.
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Actually, even though I restarted yesterday to test the functionality of
screen, I had this same problem this morning and went with the second
solution. (sudo /etc/init.d/screen-cleanup start)
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification
Um, neither one of these is a permanent fix. Once again, I have to do
one or the other.
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Reinstalling screen also worked for the new Lucid after upgrading.
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
FWIW, I just ran into this error after my computer crashed while running
an instance of screen. Fixed as discussed in this post.
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For what it's worth: I just ran into this error after upgrading to
Jaunty Alpha 2; running `sudo /etc/init.d/screen-cleanup start` manually
fixed the problem for me.
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of
This appears to be fixed since Hardy (screen 4.0.3-1):
* Recreate /var/run/screen on install/reboot if necessary (e.g. tmpfs) with
the appriopriate permissions (depending on the screen binary - some
admins might choose to install it setuid using dpkg-statoverride).
Closes:
Martin: 'It's quite obvious what the problem is though, /var/run/screen
wasn't created at install time... right?'
Not so obvious to me. The error message shows that screen tries to
create this directory, but simply can't. Looks very similar to bug
#13143, which was supposed to be solved in Hoary.
Not so obvious to me.
Well, it's obvious that /var/run/screen can't be created when screen is
run (as !root) so it must be created before that. At boot? At install
time? Don't know. But yes, if it is supposed to be created by some init
script, and isn't, perhaps finding the bug in that script
Thank you for reporting this bug. Could you please give some details ?
Knowing the release of Ubuntu and the version of 'screen' you are using
may be very helpful. Also, can you run 'sudo screen' without problems ?
** Changed in: screen (Ubuntu)
Status: New = Incomplete
--
Can't run
Thanks for your bug report!
Can you please try if «sudo screen» works? And if this works, does it
work afterwards without the sudo, too?
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I'm running a fully updated Gutsy install.
Did mkdir /var/run/screen dir, chmod 775 and chgrp to utmp. Don't see
any point in doing sudo screen after that. :) (Fixed it before filing
the bug.) I also have screen instances running right now so deleting the
dir right now isn't an option.
It's
I'm running a fully updated Gutsy install.
Fixed by mkdir /var/run/screen dir by hand, chmod 775 and chgrp to utmp.
Don't see any point in doing sudo screen at this point. :) (I fixed
it, see above, before filing the bug.) I also have screen instanses
running right now so I can't remove the dir
Bah! Ignore the first post of those two. (Stupid browser!)
--
Can't run screen in Gutsy
https://bugs.launchpad.net/bugs/172651
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Oh, and also, try to cope with by badly fast written english in the last
post. It's better than in the first but... (I hate that you can't go
back and edit comments!!! :)
Spam spam spam, wonderful spam, lovely spam, spam spam spam... :p
--
Can't run screen in Gutsy
20 matches
Mail list logo
