gwibber crashed with DBusException in call_blocking() on startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Invalid
|
Undecided
|
Unassigned | ||
gwibber (Ubuntu) |
Invalid
|
High
|
Ken VanDine |
Bug Description
Binary package hint: gwibber
gwibber 2.32.2-0ubuntu2 crashes on startup from "Internet" menu, on maverick desktop with current updates.
(The traceback looks the same as many other bugs which each have many duplicates, but they all look flagged as invalid or fix-released. As I cannot choose between them, I've opened a new report so that the experts can decide. Sorry if this makes extra work.)
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber 2.32.2-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.35-24-generic i686
Architecture: i386
Date: Mon Jan 10 01:01:26 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
LANG=en_NZ.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber crashed with DBusException in call_blocking()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
tags: | added: bugpattern-needed |
Changed in gwibber (Ubuntu): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
This crash has the same stack trace characteristics as bug #628686. 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.