If it is correct, you should not see any locked. Once you have performed the above, reset the SSH connection, and check if you get the same error. Disconnect from SSH and reconnect, check if you get the same error. If you still get the error, we are going to try the following:.
If chown is giving an error, make sure that the file is writable, by performing the following command:. Disconnect from SSH and reconnect, if the error is still there, we can try the following:. Skip to content Search for:.
Xauthority So, for the EACCES return code, obviously the first thing you check is: are my home permissions set up so I am able to write to my home directory? You should verify you have the write flag on your home directory for your own user first.
If you do, then you might be a victim of the bug described below. Through a couple google searches I was finally able to find somebody with a similar problem, and it led me to Fedora bug report. When you SSH back in, it should be fine at this point and you should be able to successfully transfer your X-session again.
Just to be as complete as possible, other users did state in the bug report that the fix above did not work for them - it happened to work for me. Another attempt to work around the problem was I did not verify this workaround personally :. Another person mentions something about GDM, which I have zero knowledge of. If that pertains to you I recommend reading his post in BugZilla and seeing if his comment means anything to you. If SELinux configuration is set to "Enforcing" it may be causing the "xauth" problem.
You can set it provisionally to "permisive" mode as follows, to be able to exclude this issue as a root cause of the problem. Then follow a SELinux tutorial to put in place a proper configuration, or disable it if you prefer another security method, f.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Ask Question. Asked 6 years, 6 months ago. Active 1 year, 8 months ago. Viewed k times. Error: Can't open display: localhost Improve this question. I found this page helpful as my issue was due to selinux being in enforcing mode, which was preventing the file from being created in the first place: twiki.
For me the problem occurred after I changed the hostname. Unfortunately the user has a directory in his home with identical name to hostname. User rights were fine, but in this circumstances X unable to start because of locking issue. Oh, and os was a Raspbian. Add a comment. Active Oldest Votes. Xauthority -rw 1 sam sam 0 Jul 12 Are you sure you want to replace the current answer with this one? Hollie's Hub for Good Supporting each other to make an impact.
Write for DigitalOcean You get paid, we donate to tech non-profits. Esto tratando de instalar en ubuntu un desktop. Estoy usando puTTY para conectarme a un server con ubuntu Xauthority I did:. Xauthority SUDO chown machine:machine. These answers are provided by our Community. If you find them useful, show some love by clicking the heart.
If you run into issues leave a comment, or add your own answer to help others. You can type! Where would you like to share this to? Twitter Reddit Hacker News Facebook. Share link Question share link. Sign Up. Yes, I'm sure.
0コメント