Bug 487152 - Refuses to run without a session bus
Refuses to run without a session bus
Product: Fedora
Classification: Fedora
Component: banshee (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Michel Alexandre Salim
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-02-24 10:42 EST by Bastien Nocera
Modified: 2009-06-06 13:13 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-06-06 13:13:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 573050 None None None Never

  None (edit)
Description Bastien Nocera 2009-02-24 10:42:03 EST

$ banshee-1 

Unhandled Exception: System.Exception: Unable to open the session message bus. ---> System.ArgumentNullException: Argument cannot be null.
Parameter name: address
  at NDesk.DBus.Bus.Open (System.String address) [0x00000] 
  at NDesk.DBus.Bus.get_Session () [0x00000] 
  --- End of inner exception stack trace ---
  at NDesk.DBus.Bus.get_Session () [0x00000] 
  at Banshee.ServiceStack.DBusConnection.get_ApplicationInstanceAlreadyRunning () [0x00000] 
  at Booter.Booter.Main () [0x00000] 

It should maybe print a warning message, but it should run nonetheless.
Comment 1 Michel Alexandre Salim 2009-02-24 10:57:39 EST
Could you provide steps to reproduce this? Is dbus not running at all?

<rant>This is why checked exception is actually a good thing</rant>
Comment 2 Bastien Nocera 2009-02-24 12:49:43 EST
$ banshee-1

D-Bus isn't running at all, I usually do, for possibly destructive tests:
$ xhost +localhost
$ su tester
# banshee-1

This is the same way I test Evolution and rhythmbox when data loss can occur (or I need them to start fast for debugging).
Comment 3 David Nielsen 2009-06-06 13:13:02 EDT
The following upstream commit to master should fix this:


We can backport the fix if it is felt to be a requirement

Note You need to log in before you can comment on or make changes to this bug.