Thanks for the bug report, but unfortunately there isn't enough
information there to determine what actually went wrong. I suspect
perhaps a race condition starting the gwibber-service, and one process
grabbed the dbus name but wasn't answering on it. But that is just
speculation, please re-open if it happens again and we can try to dig
deeper.
** Changed in: gwibber (Ubuntu)
Status: New => Incomplete
--
Gwibber service in odd state
https://bugs.launchpad.net/bugs/605422
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
