[SOLVED] After force restart GNOME doesnt' start

zayac · 2010-01-23 23:55:31

Hello!
I have a problem I can't resolve.
I restarted my pc where was opened GNOME session and next time GNOME haven't started. Just showing some startup applications ( Skype and notify window "the configuration defaults for the GNOME Power Manager have not been installed correctly. Please contact your computer administrator").

Here are some logs that could be helpful:

everything.log

Jan 24 01:42:02 pz init: Entering runlevel: 3
Jan 24 01:42:06 pz dhclient: isc-dhclient-4.1.0p1
Jan 24 01:42:06 pz dhclient: isc-dhclient-4.1.0p1
Jan 24 01:42:12 pz kernel: eth0: link down
Jan 24 01:42:13 pz kernel: agpgart-nvidia 0000:00:00.0: AGP 3.0 bridge
Jan 24 01:42:13 pz kernel: agpgart-nvidia 0000:00:00.0: putting AGP V3 device into 8x mode
Jan 24 01:42:13 pz kernel: nvidia 0000:02:00.0: putting AGP V3 device into 8x mode
Jan 24 01:42:16 pz dhcpcd: dhcpcd not running
Jan 24 01:42:18 pz gnome-session[4580]: WARNING: Error retrieving configuration key '/desktop/gnome/session/idle_delay': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Jan 24 01:42:18 pz gnome-session[4580]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
Jan 24 01:42:18 pz gnome-session[4580]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
Jan 24 01:42:19 pz dhcpcd: dhcpcd not running
Jan 24 01:42:19 pz kernel: eth0: link down
Jan 24 01:42:19 pz dhcpcd: dhcpcd not running
Jan 24 01:42:24 pz gnome-session[4580]: WARNING: No required applications specified
Jan 24 01:42:27 pz kernel: wlan0: direct probe to AP 00:03:2f:2b:9f:4d (try 1)
Jan 24 01:42:27 pz kernel: wlan0: direct probe to AP 00:03:2f:2b:9f:4d (try 2)
Jan 24 01:42:27 pz kernel: wlan0: direct probe to AP 00:03:2f:2b:9f:4d (try 3)
Jan 24 01:42:27 pz kernel: wlan0: direct probe responded
Jan 24 01:42:27 pz kernel: wlan0: authenticate with AP 00:03:2f:2b:9f:4d (try 1)
Jan 24 01:42:27 pz kernel: wlan0: authenticated
Jan 24 01:42:27 pz kernel: wlan0: associate with AP 00:03:2f:2b:9f:4d (try 1)
Jan 24 01:42:27 pz kernel: wlan0: RX AssocResp from 00:03:2f:2b:9f:4d (capab=0x431 status=0 aid=1)
Jan 24 01:42:27 pz kernel: wlan0: associated
Jan 24 01:42:28 pz dhcpcd: version 5.1.4 starting
Jan 24 01:42:28 pz kernel: fuse init (API version 7.13)
Jan 24 01:42:28 pz dhcpcd: wlan0: rebinding lease of 192.168.1.100
Jan 24 01:42:29 pz Failed: to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Jan 24 01:42:30 pz Failed: to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Jan 24 01:42:31 pz Failed: to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Jan 24 01:42:31 pz Failed: to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Jan 24 01:42:32 pz dhcpcd: wlan0: acknowledged 192.168.1.100 from 192.168.1.1
Jan 24 01:42:32 pz dhcpcd: wlan0: checking for 192.168.1.100
Jan 24 01:42:37 pz dhcpcd: wlan0: leased 192.168.1.100 for 604800 seconds
Jan 24 01:42:37 pz gnome-session[4580]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout
Jan 24 01:42:37 pz dhcpcd: forking to background
Jan 24 01:43:07 pz kernel: agpgart-nvidia 0000:00:00.0: AGP 3.0 bridge
Jan 24 01:43:07 pz kernel: agpgart-nvidia 0000:00:00.0: putting AGP V3 device into 8x mode
Jan 24 01:43:07 pz kernel: nvidia 0000:02:00.0: putting AGP V3 device into 8x mode
Jan 24 01:43:08 pz gnome-session[4953]: WARNING: Unable to determine session: Unable to lookup session information for process '4953'

In Xorg.0.log everything seems ok and there are no errors.

There is a fact, that GNOME starts successfully from another user (root). So the problem could be in user settings or some unclosed sessions. Do not know what to do from logs

Thanks in advance!

Last edited by zayac (2010-01-24 01:17:55)

scar · 2010-01-24 00:20:40

It has to be a user-specific problem

Create a regular user and test it by opening a gnome session - if it works, try to backup your inportant files/dirs in /home/YOURUSER and delete your home dir.
Maybe it is radical, but it is rather rapid too. ( if it still doesn't work, delete homedir, delete and recreate your user )

Sometimes it is faster to go around a problem than to solve it...

cesura · 2010-01-24 00:22:50

I did this too. I force restarted my pc wall gnome was running. I just made a topic about it http://bbs.archlinux.org/viewtopic.php?id=89439. Whenever I try startx now, I get a black screen with 2 small white lines at the top

scar · 2010-01-24 00:26:13

could you post your .xinitrc file?

cesura · 2010-01-24 00:30:07

Here it is:

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

exec gnome-session

I also tried the one in /etc/X11/xinit/xinitrc but that didn't work as well.

Last edited by cesura (2010-01-24 00:30:27)

zayac · 2010-01-24 01:15:02

Ok. I solved this for my issues.
The solution was found on the ubuntu forum:
http://ubuntuforums.org/showthread.php?t=1082257

What I've done is:

mv /myuser/.gconfd/saved_state /myuser/.gconfd/saved_state_backup

Then I had a completely recovered GNOME session on a next boot.

Moreover, it seems for me that saved_state could be completely removed in this case.

cesura · 2010-01-24 01:20:37

zayac wrote:

Ok. I solved this for my issues.
The solution was found on the ubuntu forum:
http://ubuntuforums.org/showthread.php?t=1082257
What I've done is:
mv /myuser/.gconfd/saved_state /myuser/.gconfd/saved_state_backup
Then I had a completely recovered GNOME session on a next boot.
Moreover, it seems for me that saved_state could be completely removed in this case.

I'm going to go try that and see if it works

cesura · 2010-01-24 01:28:50

Nope, didn't work for me. I hope I can resolve this soon, otherwise I'll have to go to debian

zayac · 2010-01-24 01:51:14

Could you post /var/log/everything.log?

cesura · 2010-01-24 02:02:39

zayac wrote:

Could you post /var/log/everything.log?

here, I uploaded because it was long
http://www.sendspace.com/file/2w3mn1

zayac · 2010-01-24 10:49:03

I haven't found something critical in everything.log, but if it has worked fine before you can try:
1. Rename directories .gnome, .gnome2, .gconf, .gconfd, and .metacity in your home and try to boot gnome.
2. Create another user and boot gnome from him. (I booted from root in this case.)

I believe it will help. If not, could you post /var/log/Xorg.0.log?

hussam · 2010-01-25 17:40:32

Same thing here. At first it appeared to be udev causing consolekit bustage, so I downgraded udev/mkinitcpio to core versions. Then rebuilt the initramfs image, restarted my PC but sadly the problem is still there. gdm is broken, anything that uses dbus or bonobo is broken...

Arch Linux

#1 2010-01-23 23:55:31

[SOLVED] After force restart GNOME doesnt' start

#2 2010-01-24 00:20:40

Re: [SOLVED] After force restart GNOME doesnt' start

#3 2010-01-24 00:22:50

Re: [SOLVED] After force restart GNOME doesnt' start

#4 2010-01-24 00:26:13

Re: [SOLVED] After force restart GNOME doesnt' start

#5 2010-01-24 00:30:07

Re: [SOLVED] After force restart GNOME doesnt' start

#6 2010-01-24 01:15:02

Re: [SOLVED] After force restart GNOME doesnt' start

#7 2010-01-24 01:20:37

Re: [SOLVED] After force restart GNOME doesnt' start

#8 2010-01-24 01:28:50

Re: [SOLVED] After force restart GNOME doesnt' start

#9 2010-01-24 01:51:14

Re: [SOLVED] After force restart GNOME doesnt' start

#10 2010-01-24 02:02:39

Re: [SOLVED] After force restart GNOME doesnt' start

#11 2010-01-24 10:49:03

Re: [SOLVED] After force restart GNOME doesnt' start

#12 2010-01-25 17:40:32

Re: [SOLVED] After force restart GNOME doesnt' start

Board footer