gwibber-service crashed with GError in notify(): 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.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gwibber
Get the error right after boot. Gwibber seems to work OK if loaded afterwards.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber-service 2.91.90-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
CheckboxSubmission: ed5dbdfb54bf504
CheckboxSystem: b633b4f40868d49
Date: Tue Mar 1 12:31:33 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber-service crashed with GError in notify(): 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.
UpgradeStatus: Upgraded to natty on 2010-11-25 (95 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #727568, so 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.