LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 06-30-2017, 06:21 PM   #1
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Manjaro
Posts: 8,914
Blog Entries: 14

Rep: Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085
Can't log in Xauth: timeout in locking authority file /home/sifu/.xauthority


Have a fresh install of Open Suse (Gecko) Linux KDE and it was running well but I couldn't access the other drives on the desktop.

Elementary OS and Voyager Linux had an id of 1000 but the fresh install of Gecko was 2001 so I fixed the uid issue with this to make all of the id's match.

Code:
usermod -u 1000 sifu
groupmod -g 1000 group
find / -user 2001 -exec chown 1000 {} \;
find / -group 2001 -exec chgrp 1000 {}
When I try to log in the screen locks up.
Dropping to tty gives me this:

Code:
xauth:timeout in locking authority file /home/sifu/.xauthority

cannot open log file /home/sifu/.local/share/xorg/.o.log please consult the x.org Foundation support http://wiki.x.org

xinit failed ./usr/bin/Xorg is not set uid, maybe that's the reason?
If so either use a display manager or adjust /etc/permissions.local and run chkstat --system --set afterwards

xauth: timeout in locking authority file /home/sifu/.Xauthority
How do I fix this?
 
Old 06-30-2017, 08:50 PM   #2
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Manjaro
Posts: 8,914

Original Poster
Blog Entries: 14

Rep: Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085
I tried the solution here (uncomment that line in /etc/permissions.local) but it didn't work.

https://forums.opensuse.org/showthre...er-start-fails
 
Old 07-01-2017, 04:12 PM   #3
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Manjaro
Posts: 8,914

Original Poster
Blog Entries: 14

Rep: Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085
Here's what I think happened.

The .Xauthority file ownership got changed to root. From what I've read online the .Xauthority file should not be owned by root that's why I can't log in.

https://askubuntu.com/questions/4369...ferred-to-root

https://askubuntu.com/questions/3006...authority-file

I know how to look at the .Xauthority file by running:
Code:
ls - la ~/
Here's what it said:
-rw-----1 1000 Network 52 Jun 30 12:53 /home/sifu/.Xauthority

As far as I can tell it is not owned by root. And I still can not log in.

Any ideas?

Last edited by Ztcoracat; 07-01-2017 at 09:26 PM.
 
Old 07-01-2017, 11:45 PM   #4
astrogeek
Moderator
 
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=14, FreeBSD_10{.0|.1|.2}
Posts: 4,807
Blog Entries: 6

Rep: Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619Reputation: 2619
Quote:
Originally Posted by Ztcoracat View Post
Here's what I think happened.

The .Xauthority file ownership got changed to root. From what I've read online the .Xauthority file should not be owned by root that's why I can't log in.

https://askubuntu.com/questions/4369...ferred-to-root

https://askubuntu.com/questions/3006...authority-file

I know how to look at the .Xauthority file by running:
Code:
ls - la ~/
Here's what it said:
-rw-----1 1000 Network 52 Jun 30 12:53 /home/sifu/.Xauthority

As far as I can tell it is not owned by root. And I still can not log in.

Any ideas?
Hi Ztcoracat!

This...

Code:
-rw-----1 1000 Network 52 Jun 30 12:53 /home/sifu/.Xauthority
Indicates (I think) that the user sifu is not the owner of the file, and that there is no user with UID 1000 on the system, otherwise it would show the user name, not the UID.

So, while that file is not owned by root, it is also not owned by the user sifu.

What does grep sifu /etc/passwd and grep 1000 /etc/passwd say?

Last edited by astrogeek; 07-01-2017 at 11:47 PM.
 
Old 07-02-2017, 12:19 AM   #5
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Manjaro
Posts: 8,914

Original Poster
Blog Entries: 14

Rep: Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085
Thank you astrogeek for chiming in-

Quote:
What does grep sifu /etc/passwd and grep 1000 /etc/passwd say?
Sorry I can't find that out as I performed a fresh install.

The other 2 os's on that machine have an id of 1000. The fresh install of Gecko linux gives a id of 2001. The last time I used those commands in post #1 to change the uid to match the other 2 it broke the Login.

I'm running Gecko Linux 42.2 XFCE on another desktop and when I ran those cmd's in tty to change the uid's it didn't break the Login.*** For some reason changing the uid in tty with Gecko Linux 42.2 KDE breaks the Login.

suicidaleggroll taught me how to fix the id issue in this thread so I know I did it correctly.
http://www.linuxquestions.org/questi...es-4175574907/
------------------------------------------------------------------------------------------------
There has got to be another way to safely change the uid. I'm thinking that I can change the uid with Yast (package mgr). I read online that some folks use Yast to do that. I just have to find out how.

-:::-So far the fresh install is working w/o any problems.-:::-
 
Old 07-03-2017, 11:35 AM   #6
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Manjaro
Posts: 8,914

Original Poster
Blog Entries: 14

Rep: Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085Reputation: 1085
Found out that there is a way to manually change users and the uid with Yast.
(any file browser, right click properties > permissions:-

Yast> Security and Users > User and Group Management.

--------------------------------------------------------------------------------------------
Doing a lot of reading online I found a few threads that suggest deleting the ~/.Xauthority file and the system will automatically create a new one at log in. That works with Ubuntu based systems systems AFAIK. I wasn't able to find concrete evidence that it wouldn't break an Open Suse (Gecko Linux) RH based system so I didn't pursue it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Xauth: timeout in locking authority file //.Xauthority v@ny@ Slackware 14 11-20-2013 06:52 AM
xauth: timeout in locking authority file ~/.Xauthority? otbibb Linux - Software 6 08-28-2013 02:42 PM
/usr/bin/xauth: timeout in locking authority file backroger Linux - Server 1 06-06-2011 11:15 PM
[SOLVED] /usr/bin/xauth: creating new authority file /home/username/.Xauthority rjo98 Linux - Newbie 9 12-21-2010 08:27 PM
xauth: timeout in locking authority file //.Xauthority karlrb Linux - Software 2 10-26-2006 07:53 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 09:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration