-
Notifications
You must be signed in to change notification settings - Fork 835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen not working #1245
Comments
You have to run it once as root |
That does not solve the problem. Upon typing Closing bash, restarting it and typing |
Could you "sudo rm /etc/hosts", restart bash.exe, and try again? Looks like that file needs to be regenerated. |
Unfortunately that doesn't seem to change the behaviour either. |
@pjacob2 Are you on the insider build or 14393. I don't think this worked yet on 14393. |
I am running Version 1607, OS Build 14393.321. |
pjacob yeah you need to upgrade to an insider build, otherwise screen is not yet supported. |
This is a duplicate of #774 |
@benhillis by now I would disagree: #774 fixed issues that prevented screen to work at all. After those were fixed, the issue was closed but left the problem Since this issue was created for this specific problem, I'd suggest to reopen it. Another option would be to reference an issue that deals with the underlying problem (I'm no expert on this but it's discussed in #774 ) so people like me who find this issue know where to look for a solution (or its status). |
By the way, |
That's #2530 |
One work-around is to do a "mkdir ~/.screen ; chmod 700 ~/.screen" and then add this to one of your shell's startup files: "export SCREENDIR=/home/USERNAME/.screen" (with the right USERNAME). |
I don't understand why this is closed, as this is still happening. |
Because dupe #2530 is open. |
Cannot make directory '/var/run/screen': Permission denied Quoting the workaround posted in the link
i added sudo /etc/init.d/screen-cleanup start to ~/.bash_profile and that seemed to do the trick |
I like WayneD's solution since it doesn't mess with the system's /run directory or the weird permission problems that screen-cleanup fixes. here's what I put in my .bashrc (a more generic solution that you can copy-pasta): export SCREENDIR=$HOME/.screen |
I can't read .screenrc. Can you? |
Same I run screen with Seems worked. |
You should make that sticky: chmod 01777 /run/screen |
I applied permission to /run/screen folder but every restart requires this fix. echo 'export SCREENDIR="$HOME/.screen"' if you start screen outside of bash like command line or scheduled task run with environment variables. C:\Users\ahmet>bash -c 'SCREENDIR=$HOME/.screen screen' |
Excellent solution I think. I add that command in my .bashrc file. |
Another method is to use the
|
When trying to run
screen
on the Windows Subsystem for Linux upon typingscreen
I get an error message stating:Typing
man screen
I do however get the manual forscreen
so it does appear to be installed.The text was updated successfully, but these errors were encountered: