gwibber-error crashed with DBusException in call_blocking()

Bug #550595 reported by Atli Þór
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

After login into Ubuntu, I get a message saying my Twitter password is incorrect. (Which is true.) Then the "crash has been detected" thing appeared in my notification area, leading me here.

Once I opened gwibber (via the "mail icon -> broadcast" thing in the notification area) and corrected the password, the feeds refuse to update even after manually selecting "Gwibber->refresh", and the "gwibber-service" is stuck at 100% CPU usage.

After killing the "gwibber-service" process and again refreshing the feed, it updates correctly and seems to be operating normally.

ProblemType: Crash
Architecture: i386
Date: Mon Mar 29 00:21:51 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-error
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.29.92.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-error
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
PythonArgs: ['/usr/bin/gwibber-error']
SourcePackage: gwibber
Title: gwibber-error crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data

Revision history for this message
Atli Þór (atli) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #547172, 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.

tags: removed: need-duplicate-check
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.