KGHtheII Posted May 21, 2008 Share Posted May 21, 2008 So this is a pretty old PC (Compaq with 900MHz AMD) but I never had this issue with previous Ubuntu versions. When I log in to the OS The screen does not fully load up, you can see the menu bars and a box but it isnt filled in with anything. After letting it sit a while, everything loads up and here is the error I see in the box: --------------------------------------------------------- There was an error starting the GNOME Settings Daemon Some things, such as themes, sounds, or background settings may not work correctly. The last error message was: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. GNOME will still try to restart the Settings Daemon next time you log in. --------------------------------------------------------- This wouldnt be a problem because everything loads up fine after a while, but it just takes too long. What is the issue? CTRL+ALT_BKSPACE doesnt fix the issue. Link to comment Share on other sites More sharing options...
Kreuger Posted May 21, 2008 Share Posted May 21, 2008 Can you get to a terminal and try to run Gnome from there to see if there's any additional output? Link to comment Share on other sites More sharing options...
KGHtheII Posted May 21, 2008 Author Share Posted May 21, 2008 Can you get to a terminal and try to run Gnome from there to see if there's any additional output? Can you tell me what you want me to type? Havent used linux in a while. Link to comment Share on other sites More sharing options...
Kreuger Posted May 21, 2008 Share Posted May 21, 2008 At the login screen, press Alt+F2 I think. Then login using the terminal. Afterwards, run startx and it should bring up Gnome. Also, the login screen should have a menu to decide what desktop environment to use, it should include terminal (fail safe). Link to comment Share on other sites More sharing options...
KGHtheII Posted May 21, 2008 Author Share Posted May 21, 2008 (edited) At the login screen, press Alt+F2 I think. Then login using the terminal. Afterwards, run startx and it should bring up Gnome. Also, the login screen should have a menu to decide what desktop environment to use, it should include terminal (fail safe). I did a login as Fail Safe GNOME and it still loaded up it said without statup scripts or something. It didnt boot up to terminal. ALT + F2 didnt do anything. I still got the same error. Edit: Sorry, I rebooted again and found FAILSAFE Terminal. So i did that and the terminal came up. But when i do a startx i get this error: --------------------------------------------------------------------------------------------- X: warning: process set to priority -1 instead of requested priority 0 Fatal Server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again --------------------------------------------------------------------------------------------- Edited May 21, 2008 by ch1ck3n Link to comment Share on other sites More sharing options...
Kreuger Posted May 21, 2008 Share Posted May 21, 2008 I believe you would just rm /tmp/.X0-lock should work without being root and cause no problems. try running startx again after Link to comment Share on other sites More sharing options...
KGHtheII Posted May 21, 2008 Author Share Posted May 21, 2008 I believe you would just rm /tmp/.X0-lock should work without being root and cause no problems. try running startx again after I removed it, then ran startx. It told me that i was running as privileged and that should be avoided, but i continued. The screen turned grey w/ a cross for a cursor, but then the same error came up. Link to comment Share on other sites More sharing options...
Fish Posted May 21, 2008 Share Posted May 21, 2008 A quick Google finds a lot of problems with this same error, and a variety of solutions. One I found that did seem to work was here http://ubuntuforums.org/showthread.php?t=587410 Link to comment Share on other sites More sharing options...
KGHtheII Posted May 21, 2008 Author Share Posted May 21, 2008 A quick Google finds a lot of problems with this same error, and a variety of solutions. One I found that did seem to work was here http://ubuntuforums.org/showthread.php?t=587410 Thanks Mr Fish but I already tried that fix before posting on here. Maybe that doesnt work because this is hardy and that worked for gutsy? I dunno. Any other suggestions? Link to comment Share on other sites More sharing options...
KGHtheII Posted May 22, 2008 Author Share Posted May 22, 2008 The following was posted on https://answers.launchpad.net/ubuntu/+question/31661 by Steve and it fixed my problem: My problem was fixed by adding the following 2 lines to /etc/network/interfaces auto lo iface lo inet loopback and then rebooting Who would have thought that it had to do with my network interfaces Thanks Link to comment Share on other sites More sharing options...
Recommended Posts