Click to See Complete Forum and Search --> : Can't log into GUI?
funky
07-12-2003, 01:07 PM
When I type the command "startx" in the shell interface I get the following error messages....
xauth: error in locking authority file /root/.Xauthority
xauth: error in locking authority file /root/.Xauthority
xauth: error in locking authority file /root/.Xauthority
xauth: error in locking authority file /root/.Xauthority
Fatal server error:
Can't read lock file /tmp/.X0-lock
When reporting a problem related to a server crash, please send the full server output, not just the last messages.
giving up
xinit: No such file or directory (errno2): unable to connect to a X server
xinit: No such process (errno3): Server error
xauth: Error in locking authority file /root/.Xauthority
DSwain
07-12-2003, 01:19 PM
What distro is it? And is the video card supported by it? If not, you won't be getting any farther than that.
why are you trying to log into X as root?
sharth
07-12-2003, 02:15 PM
rm /root/.Xauthority /root/.Xauthority ; startx
although i did notice at the bootom a /home/guest/.Xauthority
might want to check the permissions on who can run a X server.
ven0m
07-12-2003, 02:30 PM
Are you using gentoo?
if so
source /etc/profile
funky
07-12-2003, 08:03 PM
My response to everyone is:
1. I'm using Linux-Mandeake 8.1, this problem recently started after I turned off the computer accidently while I was logged into the shell interface. Mandrake 8.1 has been installed on my system for months and this is the first time I had problem logging into the GUI.
2. What difference does it make if I log into the GUI as root or ordinary user? I get this same error message when I log in as a regular user also.
3. The video card has nothing to do with it. The card is supported..
Thanks for your help everyone....but I need more info on how to correct this......
jglen490
07-12-2003, 10:40 PM
If you can sign on to the command line, cd to the /tmp directory. If there is a .Xo-lock file, delete it. Then try startx.
As to logging as root, or normal. Always log in as normal and switch to root on an as needed basis -- only -- ever.
Root has the power which both blessing and curse. If you sign on as root, and go to a network, someone could come in and take over as you as root. Also, when root, if you make a mistake, especially when removing files, the maistake can be huge. Whereas, if you are a normal user, all that can happen is that your files could be damaged, not the whole system.
I always sign on as my normal user, then do an "su -" in a terminal or let the GUI app prompt me for the root user password, but only when needed.
funky
07-13-2003, 10:35 AM
Originally posted by sharth
rm /root/.Xauthority /root/.Xauthority ; startx
although i did notice at the bootom a /home/guest/.Xauthority
might want to check the permissions on who can run a X server.
Thanks!...I'm going to give it a try....By the way, I made an error on the last line....It is indeed /root/.Xauthority.
funky
07-13-2003, 06:15 PM
YIPPEE!!!! HOORAY!!!! .......I'm back in action.....Nothing seemed to work so I booted up with the CD Boot Disc......However, when I got to the Installation Class stage, the system locked up with some sort of error message after I clicked on "UPDATE"....Boy was i pissed off now....So I rebooted, and for some reason the problem cleared up and I was able to enter into Xwindows....i wondered what happened.....
Thanks for your help everyone......
mdwatts
07-13-2003, 07:03 PM
< searching keywords >
startx Xauthority locking permission
slakrep
11-06-2003, 01:04 PM
I'm having an issue with this too. I added a user through an Xterm window in KDE. When I stopped X and tried to restart, I got "command not found". If I reboot and login as user or root, X starts fine. As soon as I SU, no X. I read about it some and I think "su" is only for switching to root while logged in as a user, not the other way around.
Slack 9.1 and XP are working great on my Dell CPx J650.
Slakrep
sharth
11-11-2003, 10:19 PM
Originally posted by slakrep
I'm having an issue with this too. I added a user through an Xterm window in KDE. When I stopped X and tried to restart, I got "command not found". If I reboot and login as user or root, X starts fine. As soon as I SU, no X. I read about it some and I think "su" is only for switching to root while logged in as a user, not the other way around.
Slack 9.1 and XP are working great on my Dell CPx J650.
Slakrep "su -" probably will fix those problems.