Unable to open the session message bus

Bug #86172 reported by hanzomon4
2
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

Binary package hint: dbus

I'm having problems with with certain apps not being able to "open the session message bus". I get this with banshee, last-exit, and probably others too. I discovered that "dbus-launch app-name" will get the app to start.

I'll attach the error message.......

This is in feisty fawn, I'm not sure how to specify that here.

Revision history for this message
hanzomon4 (hanzomon4) wrote :
description: updated
Revision history for this message
Sebastian Dröge (slomo) wrote :

Do you also have this with... say... "dbus-monitor --session"?
dbus-monitor is in dbus-1-utils

What does "ps aux | grep dbus" show? Does /etc/X11/Xsession.options contain use-session-dbus?

Changed in dbus:
status: Unconfirmed → Needs Info
Revision history for this message
hanzomon4 (hanzomon4) wrote :

I get an error but it doesn't appear to be the same as the other error messages. I'll attach the out put of both commands...

Revision history for this message
hanzomon4 (hanzomon4) wrote :
Revision history for this message
hanzomon4 (hanzomon4) wrote :

Strange, after a reboot it appears to have fixed it self. I guess you can close this bug, I'll keep you posted if it ever returns.

Revision history for this message
Brian Murray (brian-murray) wrote :

This bug report is being closed due to your last comment regarding this being fixed with a reboot. Thanks again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in dbus:
assignee: nobody → brian-murray
status: Needs Info → Rejected
Revision history for this message
jan-teichmann (teichmann-jan) wrote :

Hi
i have nearly the same problem: After log in the gnome session is loading and i get the following message:

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.

Failed to open connection to session message bus: Failed to connect to socket /tmp/dbus-2NfnU1GkS2: Connection refused

after a reboot al seems to be fine again. this problem happens 3 or 4 times a week.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.