gwibber-service 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.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
gwibber-service crashed with DBusException in call_blocking(): org.freedesktop
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber-service 3.1.4+r1083-
ProcVersionSign
Uname: Linux 3.0.0-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Tue Aug 2 04:09:38 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110731)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
LANG=ro_RO.UTF-8
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber-service crashed with DBusException in call_blocking(): org.freedesktop
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
gwibber.log:
2011-08-02 04:09:12,777 - Gwibber Service - INFO - Running from the system path
2011-08-02 04:09:38,760 - Gwibber Service - INFO - Running from the system path
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 #741621, 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.