This happens when there is already running instance of GTG. GTG detects this, try to show the task browser of the other instance of GTG and then close. In some very rare and special conditions it is possible to detect other versions of GTG which has a different DBus interface and there is a traceback.
The solution to this problem is to catch the exception and exit the GTG without it. (Because other instance of GTG is running). I provide a patch for this, it is included in the current trunk version GTG. You are able to reproduce this behavior: 1, update gtg.pid file in XDG_DATA_HOME to PID of some running process which has GTG in its CMD, e.g. launch vim gtg.txt 2, run GTG ** Patch added: "dbus-traceback.patch" https://bugs.launchpad.net/ubuntu/+source/gtg/+bug/636554/+attachment/2489388/+files/dbus-traceback.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636554 Title: gtg crashed with DBusException in call_blocking() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtg/+bug/636554/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
