Xauth error in locking authority file .xauthority

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:. You could disable X-forwarding in your SSH config for this server. Dmitri Chubarov Dmitri Chubarov 2, 1 1 gold badge 13 13 silver badges 28 28 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. I can gladly give you all the information you need. Show 1 more comment. Sign up or log in Sign up using Google.

Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science.

Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked Related 6. I came across this post titled: xauth: error in locking authority file.

Xauthority [linux, ssh, X11] which mentions the use of xauth -b to break any lock files that may be hanging around. I have another answer to the question that plagued me before I figure out the issue. The issue is a bug in Fedora OS and it's derivatives, as I later figured out. As user slm said, running strace will give you an indication of the issue, but in this particular bug's case, the output is different:. 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.