Unfortunately this error could be caused by many reasons and should be
transient. So hard to reproduce. For gwibber 3.2 we will do some re-
factoring to make this much more resilient.
** Changed in: gwibber (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757842
Title:
gwibber-accounts crashed with DBusException in call_blocking():
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.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
