listen doesn't start with some python errors

[lunarok]

Binary package hint: listen

I am using xubuntu 9.10, I have this error :

/usr/lib/pymodules/python2.6/musicbrainz2/model.py:21: DeprecationWarning: the sets module is deprecated
  from sets import Set
Traceback (most recent call last):
  File "listen", line 153, in listen_is_alive
    pid = int(pf.read().strip())
ValueError: invalid literal for int() with base 10: ''
Traceback (most recent call last):
  File "listen", line 200, in <module>
    ListenApp()
  File "listen", line 141, in __init__
    self.option.run_load()
  File "/usr/lib/listen/option_parser.py", line 113, in run_load
    obj = bus.get_object("org.gnome.Listen","/org/gnome/listen")
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  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.

I try under ubuntu 9.10 and it's working ...
Without musibrainz2 (message saying it's deprecated, just complain about the fact module is not here but still same messages after)

[Mitch Towner (kermiac)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 521026, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.