gwibber crashed with DBusException in call_blocking()

Bug #539781 reported by Ryan Steele on 2010-03-16
This bug affects 35 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Ken VanDine

Bug Description

Binary package hint: gwibber

gwibber-service crashes on startup, causing the client to crash as well.

ProblemType: Crash
Architecture: amd64
Date: Tue Mar 16 11:33:48 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
Package: gwibber
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Ryan Steele (rgsteele) wrote :

This crash has the same stack trace characteristics as bug #532133. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: removed: need-duplicate-check
tags: added: regression-retracer
visibility: private → public
Christoph Korn (c-korn) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gwibber (Ubuntu):
status: New → Incomplete
Ryan Steele (rgsteele) wrote :

Christoph, I think this is another case of Gwibber not dealing with the case where the daemon has gone down (see Bug #439325). The crash happens on startup before any UI is displayed and is accompanied by the crash of gwibber-service.

Changed in gwibber (Ubuntu):
status: Incomplete → Confirmed
Ken VanDine (ken-vandine) wrote :

This traceback looks valid, it couldn't start the service. We need to figure out why the service failed to start. Please attach the gwibber log file located at $HOME/.cache/gwibber/gwibber.log


Ryan Steele (rgsteele) wrote :

Software development best practices dictate that an application should never throw an unhandled exception. In this case, the application should probably display an error message indicating that the service could not be started.

As requested, I've attached the gwibber.log file, but you may want to see Bug #524011 which is the report for the corresponding crash of gwibber-service.

Changed in gwibber (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
importance: Undecided → Medium
tags: added: bugpattern-needed
André Gondim (andregondim) wrote :

I have problem with gwibber, my log at attach.


Brian Curtis (bcurtiswx) wrote :

Ken, anything new here?

Changed in gwibber (Ubuntu):
importance: Medium → High
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gwibber - 2.29.95-0ubuntu5

gwibber (2.29.95-0ubuntu5) lucid; urgency=low

  * debian/patches/lp_539781.patch
    - Fix handling of raising the keyring error (LP: #539781)
  * debian/patches/lp_560008.patch
    - Removed, incorporated in lp_539781.patch
 -- Ken VanDine <email address hidden> Wed, 14 Apr 2010 11:22:09 -0400

Changed in gwibber (Ubuntu):
status: Confirmed → Fix Released
Mark Cariaga (mzc) wrote :

This bug is still recurring. approt has reported gwibber crashed after failing to open at start-up

well gwibber 2.30 is not yet build build so please wait a couple of hours
for it to build and reach your mirror.

sara (ms-sara-griffin) wrote :

this is coninueing

Also got this error on April 17. Though through retries Gwibber eventually ran.

Changed in gwibber (Ubuntu):
status: Fix Released → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers