gwibber crashed with DBusException in call_blocking()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gwibber
1.- Description: Ubuntu lucid (development branch)
Release: 10.04
2.- gwibber:
Instalados: 2.29.95-0ubuntu1
Candidato: 2.29.95-0ubuntu1
Tabla de versión:
*** 2.29.95-0ubuntu1 0
500 http://
100 /var/lib/
3.- open dialog gwibber
4.- i updated from karmic to lucid with alt+f2 "update-manager -d" after that try to open gwibber and doesn't work
if i execute in terminal i obtain this :
~$ gwibber
** (gwibber:3081): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:3081): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:3081): WARNING **: Trying to register gtype 'WnckWindowMove
No dbus monitor yet
Updating...
ERROR:dbus.
Traceback (most recent call last):
File "/usr/bin/gwibber", line 67, in <module>
client.Client()
File "/usr/lib/
self.w = GwibberClient()
File "/usr/lib/
self.model = gwui.Model()
File "/usr/lib/
self.services = json.loads(
File "/usr/lib/
return self._proxy_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gwibber 2.29.95-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Apr 10 00:48:58 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
LANG=es_ES.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: gwibber
Title: gwibber crashed with DBusException in call_blocking()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #539781, 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.