gwibber (daily build) fails to start in Debian

[Kartik Mistry]

Background Note: I'm packaging gwibber2 for Debian. The main blocking point 'desktopcouch' package has been packaged and upload to Debian, but it yet to accept in Debian. I've that package installed however.

I rebuilt gwibber-daily package from source and installed properly.

While running it,

$ gwibber -v -d
DEBUG:root:Launched from /usr/bin
ERROR:dbus.proxies:Introspect error on :1.2:/: 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.
DEBUG:dbus.proxies:Executing introspect queue due to error
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 47, in <module>
    cdb.getPort()
  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 622, 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.

Let me know what more information I can give :)

[Martey Dodoo (martey)]

This looks like the same as bug #519557, I think.

[Omer Akram (om26er)]

Can you please confirm if this is still an issue?

[Omer Akram (om26er)]

thanks for the bug report this particular bug has already been reported but feel free to report any other bugs you may find