"Can't read lock file /tmp/.X0-lock"

"Can't read lock file /tmp/.X0-lock"

Post by Arild Jens » Thu, 22 Feb 1996 04:00:00

When I type "startx" I get this error message:

Fatal server error:
Can't read lock file /tmp/.X0-lock

What is wrong? If I touch /tmp/.X0-lock, I get X up and running, but after I
quit, the file disappears. Same thing happens regardless if I'm the root or
a normal user.

I'm using Slackware 3.0.

Please e-mail any responses.

Thank you!

-Arild Jensen


1. Where is /tmp/.X0-lock with R6

   The Xservers in R6 do not create a /tmp/.X0-lock file when started.  They
did in R5.  Has there been a replacement for this file in R6, or am I doing
something wrong.  This seems to cause problems for xdm.  When I exit my X
session it takes about 5 minutes for the x-login prompter to come back to
the screen.

-Steven Clarke    

 ^[:wq!     Crap!  Thought I was in vi.  

                                                             -Stevie Nicks

2. Apache, PHP and CGI security

3. Can't open "/usr/local/news/locks/LOCK.newgroup.log"

4. PAP authentication problems

5. Lock failure on "lists/freebsd-ports.spool.lock"

6. history key

7. !!!! kppp- "Sorry, can't create modem lock file"...HELP!

8. press function key F1,then send a string instead of a char, how?

9. More problems, COM4 (cua3) is always "busy" or "locked"

10. High-Res-Timers: Unexpected "lock" during "Calibrating delay loop "

11. SMAIL problems: "lock failed", and "network is unreachable."

12. get rit of "lock the desktop" and "logout"

13. "double lock on device queue!", "Socket destroy delayed"