Crash when d-bus is not running: $DBUS_SESSION_BUS_ADDRESS left empty. Unable to open the session message bus. ---> ArgumentNullException
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tomboy (Arch Linux) |
New
|
Undecided
|
Unassigned | ||
tomboy (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: tomboy
$ tomboy
Unhandled Exception: System.Exception: Unable to open the session message bus. ---> System.
Parameter name: address
at NDesk.DBus.Bus.Open (System.String address) [0x00000] in <filename unknown>:0
at NDesk.DBus.
--- End of inner exception stack trace ---
at NDesk.DBus.
at NDesk.DBus.
at Tomboy.
at Tomboy.
at Tomboy.Tomboy.Main (System.String[] args) [0x00000] in <filename unknown>:0
I expected this to start 'tomboy', like it used to in 10.04. I don't normally run gnome-session, but I tried to start it just to see if that would fix it, but I got the same behavior. This is on Ubuntu 10.10, (Architecture: amd64, Version: 1.4.0-0ubuntu2).
summary: |
- Tomboy crashes because it can't connect to session(?) + Tomboy crashes is d-bus session is not running |
summary: |
- Tomboy crashes is d-bus session is not running + Tomboy crashes when d-bus session is not + running$DBUS_SESSION_BUS_ADDRESS left empty. Unable to open the session + message bus. ---> ArgumentNullException |
summary: |
- Tomboy crashes when d-bus session is not - running$DBUS_SESSION_BUS_ADDRESS left empty. Unable to open the session - message bus. ---> ArgumentNullException + Crash when d-bus is not running: $DBUS_SESSION_BUS_ADDRESS left empty. + Unable to open the session message bus. ---> ArgumentNullException |
You appear to not have your d-bus session running