Bug#548446: [gnome-session] Gnome doesn't start since gnome-session upgrade
Hi! This bug just exhibited itself when upgrading from an older version of Gnome2 to the current testing 2.28.0-6. Gnome starts fine for a user with a freshly created account but hangs just after displaying the background image with accounts with old Gnome2 configuration present. In my case the solution was to remove the following files/directories: ~/.nautilus ~/.gconf/%gconf-tree.xml ~/.gconf/apps/panel Cheers, -- Juhan Ernits The additional symptoms of the hang were devkit-disks-daemon and dbus-daemon taking ~20% each of cpu: root 14298 4.0 0.1 5048 2864 ?S09:55 1:14 /usr/lib/devicekit-disks/devkit-disks-daemon root 14299 0.0 0.0 4784 716 ?S09:55 0:00 devkit-disks-daemon: polling /dev/sr0 juhan 2743 0.0 0.0 2844 572 ?S10:26 0:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session juhan 2743 0.0 0.0 2844 572 ?S10:26 0:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session juhan31589 5.2 0.0 2844 1092 ?Ss 10:25 0:03 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session .xsession-errors had repeated errors of the following flavour: (gnome-panel:5469): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.68 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts (nautilus:5470): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (nautilus:5470): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.70 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts (gnome-panel:5469): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) (gnome-panel:5469): GVFS-RemoteVolumeMonitor-WARNING **: New owner :1.70 for volume monitor org.gtk.Private.GduVolumeMonitor connected to the bus; seeding drives/volumes/mounts -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=et_EE.ISO-8859-15, LC_CTYPE=et_EE.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-session depends on: ii gnome-panel 2.28.0-3 launcher and docking facility for ii gnome-session-bin 2.28.0-6 The GNOME Session Manager - Minima ii gnome-session-common 2.28.0-6 Common files for the GNOME session ii gnome-settings-daemon 2.28.1-2 daemon handling the GNOME session ii metacity 1:2.28.0-3 lightweight GTK+ window manager ii nautilus 2.28.4-1 file manager and graphical shell f ii policykit-1-gnome 0.96-2 GNOME authentication agent for Pol Versions of packages gnome-session recommends: ii gnome-power-manager 2.28.3-2 power management tool for the GNOM Versions of packages gnome-session suggests: ii desktop-base 5.0.5 common files for the Debian Deskto ii gnome-keyring 2.28.2-1 GNOME keyring services (daemon and ii gnome-user-guide 2.28.2-1 GNOME user's guide -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade
Le samedi 26 septembre 2009 à 09:00 -0400, Wendy Elmer a écrit : I removed gnome-power-manager and the message went away but gnome still hangs on starting. No backgrounds, splashscreens, panels, etc come up. All that happens is that the screen changes to a solid color and I see the mouse. There are no error messages. The screen just hangs. I can do ctl-alt-F1 and go to a terminal session and restart gdm and log into the other userid. Are there any gnome logs I can look at for the failing userid? Look at ~/.xsession-errors after the lockup. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade
Package: gnome-session Version: 2.26.2-1 Severity: grave --- Please enter the report below this line. --- Gnome doesn't start for one of the userids on my computer since the last gnome upgrades in squeeze. Another of the users on the computer has no problems. On the session that won't start, an error is coming up: Install problem The configuration defaults for GNOME power manager have not been installed correctly. Please contact your computer administrator. I removed gnome-power-manager and the message went away but gnome still hangs on starting. No backgrounds, splashscreens, panels, etc come up. All that happens is that the screen changes to a solid color and I see the mouse. There are no error messages. The screen just hangs. I can do ctl-alt-F1 and go to a terminal session and restart gdm and log into the other userid. Are there any gnome logs I can look at for the failing userid? --- System information. --- Architecture: i386 Kernel: Linux 2.6.30.090903 Debian Release: squeeze/sid 500 testing security.debian.org 500 testing debian.yorku.ca 500 testing debian-multimedia.org 500 intrepidppa.launchpad.net --- Package information. --- Depends(Version) | Installed -+-=== gnome-settings-daemon (= 2.26) | 2.26.1-2 gnome-panel | 2.26.3-1 metacity | 1:2.26.0-3 OR compiz-gnome | 0.8.2-6 OR sawfish | gnome-session-bin (= 2.26) | 2.26.2-1 gnome-session-bin ( 2.27) | 2.26.2-1 Package's Recommends field is empty. Suggests (Version) | Installed -+-=== gnome-user-guide | 2.26.2-1 OR gnome2-user-guide| desktop-base | 5.0.5 gnome-keyring| 2.26.1-1
Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade
On Sat, 2009-09-26 at 15:42 +0200, Josselin Mouette wrote: Le samedi 26 septembre 2009 à 09:00 -0400, Wendy Elmer a écrit : I removed gnome-power-manager and the message went away but gnome still hangs on starting. No backgrounds, splashscreens, panels, etc come up. All that happens is that the screen changes to a solid color and I see the mouse. There are no error messages. The screen just hangs. I can do ctl-alt-F1 and go to a terminal session and restart gdm and log into the other userid. Are there any gnome logs I can look at for the failing userid? Look at ~/.xsession-errors after the lockup. Cheers, Here is the error file. /etc/gdm/Xsession: Beginning session setup... GConf Error: 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)) GConf Error: 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)) x-session-manager[9253]: 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)) GConf Error: 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)) x-session-manager[9253]: WARNING: Could not parse desktop file /home/brent/.config/autostart/sudo.desktop: Key file does not have key 'Type' x-session-manager[9253]: WARNING: could not read /home/brent/.config/autostart/sudo.desktop x-session-manager[9253]: WARNING: Could not parse desktop file /home/brent/.config/autostart/cgmailservice.desktop: Key file does not have key 'Type' x-session-manager[9253]: WARNING: could not read /home/brent/.config/autostart/cgmailservice.desktop GConf Error: 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)) GConf Error: 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)) GConf Error: 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)) GConf Error: 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)) GConf Error: 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)) GConf Error: 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)) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have
Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade
Le samedi 26 septembre 2009 à 17:45 -0400, Wendy Elmer a écrit : Here is the error file. GConf Error: Failed to contact configuration server This is probably because D-Bus is not started. Is the startup mechanism overriden in anyway? What’s in .dmrc, .xsessionrc, .gnomerc, .xsession, .xinitrc? Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade
On Sun, 2009-09-27 at 00:17 +0200, Josselin Mouette wrote: Le samedi 26 septembre 2009 à 17:45 -0400, Wendy Elmer a écrit : Here is the error file. GConf Error: Failed to contact configuration server This is probably because D-Bus is not started. Is the startup mechanism overriden in anyway? What’s in .dmrc, .xsessionrc, .gnomerc, .xsession, .xinitrc? Cheers, .dmrc is the only one that exists. Here are the contents: [Desktop] Session=default I am trying to google for the error. I found this but it didn't seem to do anything. https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/336660
Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade
Le samedi 26 septembre 2009 à 20:34 -0400, Wendy Elmer a écrit : On Sun, 2009-09-27 at 00:17 +0200, Josselin Mouette wrote: Le samedi 26 septembre 2009 à 17:45 -0400, Wendy Elmer a écrit : Here is the error file. GConf Error: Failed to contact configuration server This is probably because D-Bus is not started. .dmrc is the only one that exists. Here are the contents: OK, then what is the process list of your user when this happens? -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Bug#548446: [gnome-session] gnome doesn't start since gnome-session upgrade
On Sun, 2009-09-27 at 03:11 +0200, Josselin Mouette wrote: Le samedi 26 septembre 2009 à 20:34 -0400, Wendy Elmer a écrit : On Sun, 2009-09-27 at 00:17 +0200, Josselin Mouette wrote: Le samedi 26 septembre 2009 à 17:45 -0400, Wendy Elmer a écrit : Here is the error file. GConf Error: Failed to contact configuration server This is probably because D-Bus is not started. .dmrc is the only one that exists. Here are the contents: OK, then what is the process list of your user when this happens? PID TTY STAT TIME COMMAND 8913 ?S 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login 8924 ?Ss 0:00 x-session-manager 9095 ?Ss 0:00 /usr/bin/ssh-agent /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager 9096 ?Ss 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager 9101 ?Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session 9104 ?S 0:00 /usr/bin/dbus-launch --exit-with-session x-session-manager 9227 ?Ss 0:00 /usr/lib/gnome-settings-daemon/gnome-settings-daemon 9281 ?S 0:00 /usr/lib/notification-daemon/notification-daemon 9350 ?Ssl 0:00 /usr/bin/pulseaudio --start 9351 ?S 0:00 python /usr/share/screenlets-manager/screenlets-daemon.py 9352 ?S 0:00 gnome-volume-control-applet 9358 ?S 0:00 nm-applet --sm-disable 9363 ?S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper 9768 tty1 R 0:00 -bash 9969 tty1 R+ 0:00 ps U brent here is ps -aef | grep dbus before login: 105 2835 1 0 21:01 ?00:00:00 /usr/bin/dbus-daemon --system here is ps -aef | grep dbus after login hangs: 105 2835 1 0 21:01 ?00:00:00 /usr/bin/dbus-daemon --system brent 5756 5472 0 21:03 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager brent 5757 5472 0 21:03 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager brent 5760 1 0 21:03 ?00:00:00 /usr/bin/dbus-launch --exit-with-session x-session-manager brent 5761 1 1 21:03 ?00:00:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session brent 6262 5287 0 21:03 tty1 00:00:00 grep dbus
