Getting this error message: Could not create lock file in /tmp/.tX0-lock
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mint 16 on my main box, Pepermint & EasyPeasy on an Acer Netbook.
Posts: 7
Rep:
Getting this error message: Could not create lock file in /tmp/.tX0-lock
I had problems with my HP desktop machine last night while running Mint 16. The problems resulted in me being forced to do a hard-power button shut down of the machine. When I tried to get back on I got the splash screen and the login screen. Logging in takes me to a black window where only the mouse cursor is visible.
Alt+ctrl+f2 takes me into the terminal. Running "Startx" brings up the following error message:
(EE)
Fatal server error:
(EE) Could not create lock file in /tmp/.tX0-lock
xinit: giving up
xinit: unable to connect to x server: Connection refused
xinit: server error
xauth error in locking authority file /root/.Xauthority
I have tried to uninstall, reinstall and reconfigure xorg but nothing is working.
1) you have a corrupted system... but I'm not sure where the corruption is. One possibility is to "rm -f /tmp/.X*" Be careful when you type this...
This is best done in single user mode, then resume the boot (just use control-d). This may correct the problems.
2) startx by default tries to create display :0.0, this is also the display created by the login - you can't do both. You can try "startx -- -display :1.0", but with some of the other corruption you have (the desktop thing) it may not work any better.
Distribution: Mint 16 on my main box, Pepermint & EasyPeasy on an Acer Netbook.
Posts: 7
Original Poster
Rep:
Quote:
Originally Posted by jpollard
1) you have a corrupted system... but I'm not sure where the corruption is. One possibility is to "rm -f /tmp/.X*" Be careful when you type this...
This is best done in single user mode, then resume the boot (just use control-d). This may correct the problems.
2) startx by default tries to create display :0.0, this is also the display created by the login - you can't do both. You can try "startx -- -display :1.0", but with some of the other corruption you have (the desktop thing) it may not work any better.
Thanks. I'll give your suggestion a try but have an idea I'll be doing a fresh install and saying goodbye to all my programs. Perhaps I'll go back to Mint 13, at least I knew that was working.
I have the same Errore on Debian8, the solution unfortunatly not work by me.
I give her my solution:
Just wanted to say thanks to @tockati even though he might not be around.
I had similar problems like the op, which led me to this thread. Video editor crashed unexpectedly several times. I rebooted and GUI kept looping my login window even though I used right crendentials. Running "Startx" displayed the same error message as above.
I took small steps via Google, tried df -h, noticed full disk and did some cleaning up.
Not in a million years I could have guessed that low disk space would create such login symptoms.
Just wanted to say thanks to @tockati even though he might not be around.
I had similar problems like the op, which led me to this thread. Video editor crashed unexpectedly several times. I rebooted and GUI kept looping my login window even though I used right crendentials. Running "Startx" displayed the same error message as above.
I took small steps via Google, tried df -h, noticed full disk and did some cleaning up.
Not in a million years I could have guessed that low disk space would create such login symptoms.
Only because the GUI startup has to create files for authorization and domain socket definitions for communication (the socket itself only needs an inode, but sometimes the directory that entry is put in must be created and/or have some block(s) allocated for the name. Other things also happen at the same time - the GUI startup tends to create a log file for errors, and that can cause the GUI to abort.
The same thing can happen with CLI logins when /var is full. The login/tty cannot add the audit records will cause the login to fail.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.