GTG says it's already running when trying to restart it

[ignoble]

After I close GTG using the normal "x" button, it is not possible to start the program again; not even when I logoff and login; I need to restart the computer.
When I try to start GTG on the command line after having it closed, it tells me "Getting Things Gnome! läuft bereits!" which is German for "Getting Things Gnome! is already running!"

I'm running GTG 0.2.4 from the official Ubuntu lucid repository; no PPA.
I have installed Ubuntu Netbook Edition 10.04.1.

$ gtg -d
2010-12-15 10:18:23,922 - DEBUG - gtg:main:105 - Debug output enabled.
Getting Things Gnome! läuft bereits!
^CTraceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 574, in msg_reply_handler
    def msg_reply_handler(message):
KeyboardInterrupt
Traceback (most recent call last):
  File "/usr/bin/gtg", line 52, in <module>
    sys.exit(GTG.gtg.main(options, args))
  File "/usr/share/gtg/GTG/gtg.py", line 108, in main
    check_instance(config.DATA_DIR)
  File "/usr/share/gtg/GTG/gtg.py", line 85, in check_instance
    d.show_task_browser()
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

As you can see in the output, I pressed Ctrl+C because after the message it was already running nothing happens. After some minutes I got the rest of the output. I tried it a second time after that, but I got the same output.

[Lionel Dricot (ploum-deactivatedaccount)]

does this bug still happen?

[Izidor Matušov (izidor)]

I encounter similar tracebacks when GTG is already running and DBus versions are different, methods are added/missing. In this case GTG should just gracefully degrade - turn silently off...

Fixed in rev. 971