LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 02-21-2014, 06:12 PM   #1
matt00
LQ Newbie
 
Registered: Aug 2009
Location: Western New York
Distribution: Mint 16 on my main box, Pepermint & EasyPeasy on an Acer Netbook.
Posts: 7

Rep: Reputation: 0
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.

Any suggestions?
 
Old 02-21-2014, 06:56 PM   #2
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,912

Rep: Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513
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.
 
Old 02-21-2014, 08:15 PM   #3
matt00
LQ Newbie
 
Registered: Aug 2009
Location: Western New York
Distribution: Mint 16 on my main box, Pepermint & EasyPeasy on an Acer Netbook.
Posts: 7

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by jpollard View Post
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.
 
Old 08-21-2015, 12:51 PM   #4
tockati
LQ Newbie
 
Registered: Aug 2015
Posts: 1

Rep: Reputation: Disabled
Smile Same Error on Debian8

I have the same Errore on Debian8, the solution unfortunatly not work by me.

I give her my solution:

Code:
sudo apt-get update
sudo apt-get -y dist-upgrade
sudo apt-get autoremove
sudo apt-get autoclean
and then:

Code:
startx
remove the disque space for exemple remove files for the basket.


sory for my bad English

Last edited by tockati; 08-21-2015 at 12:52 PM. Reason: error
 
Old 08-21-2015, 01:06 PM   #5
fatmac
Senior Member
 
Registered: Sep 2011
Location: Upper Hale, Surrey/Hants Border, UK
Distribution: Devuan (mainly)
Posts: 4,340

Rep: Reputation: Disabled
Quote:
Fatal server error:
(EE) Could not create lock file in /tmp/.tX0-lock
It can't create it because it still exists from your previous session.
Check for & delete that file & you should be able to start X again.
 
Old 10-21-2018, 05:23 PM   #6
TeTaFI
LQ Newbie
 
Registered: Aug 2015
Posts: 11

Rep: Reputation: 0
Quote:
Originally Posted by tockati View Post
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.
 
Old 10-22-2018, 05:12 AM   #7
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,912

Rep: Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513Reputation: 1513
Quote:
Originally Posted by TeTaFI View Post
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.
 
Old 10-24-2018, 06:56 PM   #8
Habitual
LQ Veteran
 
Registered: Jan 2011
Location: Abingdon, VA
Distribution: Catalina
Posts: 9,374
Blog Entries: 37

Rep: Reputation: Disabled
Quote:
Originally Posted by matt00 View Post
Perhaps I'll go back to Mint 13, at least I knew that was working.
EOL.

I'd move up to an LTS release.
 
  


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
deian yum lock [ ERR] Reading state information E: Could not get lock /var/lock/aptit jayakumar01 Linux - Server 1 12-05-2011 12:26 PM
[SOLVED] Can't read lock file tmp .x0-lock xinit: stale nfs file handle everal Slackware 2 10-31-2011 08:11 AM
Fedora 8 and NoMachine "Could not create lock file in /tmp/.tX1002-lock" ln3wb13 Linux - Software 3 05-17-2008 02:31 PM
Can't read lock file /tmp/.X0-lock squinn Linux - Newbie 3 07-13-2004 04:42 PM
can't create lock file? Class Zero Linux - Newbie 3 01-30-2002 06:24 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:50 PM.

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
Open Source Consulting | Domain Registration