gwibber-error crashed with DBusException in call_blocking()

Bug #553069 reported by Jason S. Wagner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

I had just configured my Identi.ca details on a clean installation from 20100331.2 daily live ISO. The authentication failed and I attempted to open the configuration window again when this crash occurred. This is probably a duplicate of the other similarly titled bugs, but I couldn't confirm from the information I saw. If so, feel free to confirm and close.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gwibber 2.29.94-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Mar 31 23:41:33 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-error
InstallationMedia:

InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-error
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
PythonArgs: ['/usr/bin/gwibber-error']
SourcePackage: gwibber
Title: gwibber-error crashed with DBusException in call_blocking()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jason S. Wagner (jasonswagner) wrote :
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
visibility: private → public
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.