banshee-1.4.2-3.fc10.x86_64 $ 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.
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>
$ unset DBUS_SESSION_BUS_ADDRESS $ banshee-1 D-Bus isn't running at all, I usually do, for possibly destructive tests: $ xhost +localhost $ su tester <snip> # 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).
The following upstream commit to master should fix this: http://git.gnome.org/cgit/banshee/commit/?id=7c92c2a5eb783f4220a4a80d48258d555f83e78a We can backport the fix if it is felt to be a requirement