[ubuntu-mono] [Bug 660536] Re: Tomboy crashes because it can't connect to session(?)

crane cai caizimin at gmail.com
Tue Oct 26 22:02:43 UTC 2010


Hi Armstrong,

I met the same error when using Ubuntu 10.10 without gnome window
manager. I use awesome instead which will not launch gnome-session. And
it will cause the error.

Other finding are:
* if launch gnome-session manually, then in another terminal, I launch tomboy same error.
* if Iaunch gnome-session manully, then an gnome-applet occurs which launched by gnome-session, touch the tomboy icon in panel, tomboy launch well.

Brs,
-Crane

-- 
Tomboy crashes because it can't connect to session(?)
https://bugs.launchpad.net/bugs/660536
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to tomboy in ubuntu.

Status in “tomboy” package in Ubuntu: New
Status in “tomboy” package in Arch Linux: New

Bug description:
Binary package hint: tomboy

$ tomboy

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] in <filename unknown>:0 
  at NDesk.DBus.Bus.get_Session () [0x00000] in <filename unknown>:0 
  --- End of inner exception stack trace ---
  at NDesk.DBus.Bus.get_Session () [0x00000] in <filename unknown>:0 
  at NDesk.DBus.BusG.Init () [0x00000] in <filename unknown>:0 
  at Tomboy.GnomeApplication.Initialize (System.String locale_dir, System.String display_name, System.String process_name, System.String[] args) [0x00000] in <filename unknown>:0 
  at Tomboy.Application.Initialize (System.String locale_dir, System.String display_name, System.String process_name, System.String[] args) [0x00000] in <filename unknown>:0 
  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).






More information about the Ubuntu-mono mailing list