GNOME Bugzilla – Bug 546393
2.23.6 doesn't start
Last modified: 2008-08-08 17:53:37 UTC
gnome-session 2.23.5 and a gnome-session-dbus snapshot taken on 20080731 start correctly on the same box, the new 2.23.6 displays this error "Could not connect to session bus: Failed to connect to socket /tmp/dbus-randomchars: Connexion refused" then this one "Could not acquire name on the session bus: Failed to connect to socket /tmp/dbus-randomchars: Connexion refused" and when clicking on the button to acknowledge the second dialog the dialog hangs and the session login doesn't continue
As a result of bug #360475 gnome-session does not explicitly start the session bus anymore. It should be started before gnome-session is run. However, it looks like you do have a session bus running but gnome-session doesn't have permission to connect to it. Any idea why this might be?
couldn't the code still do whatever it was doing to have a working dbus if it doesn't find a bus where it can connect? the change is likely to let quite some users stucked having a GNOME where they can't log in without any clue on how to fix the situation
Well, I think that if there is a system configuration problem that prevents the first session bus from working there is certainly no guarantee that the next one will. Do you know why it wasn't working for you?
the error is misleading, there is simply no session bus running indeed why that's not working? because ubuntu doesn't start dbus at the moment since it was stated on bug #360475 that gnome-session should be doing that, we will change dbus to be started again but dbus-x11 is a separate binary on debian and ubuntu and users can uninstall it if they want, it's likely going to create trouble for the users who didn't install it or modified their configuration, would be nice to handle the situation in a nicer way
Marking as a dup of a later bug simply because it has some more useful information in it from Ray and Colin. *** This bug has been marked as a duplicate of 546863 ***