gwibber-service crashed with DBusException in call_blocking()

Bug #519557 reported by Mahesh Asolkar
512
This bug affects 114 people
Affects Status Importance Assigned to Milestone
Gwibber
New
Undecided
Unassigned
gwibber (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: gwibber

Just installed updates. On starting GNOME desktop, I got this crash. I was also trying to click on 'Chat Accounts...' and 'Broadcast Accounts...' on the 'me' panel applet.

ProblemType: Crash
Architecture: i386
Date: Tue Feb 9 15:08:21 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
InterpreterPath: /usr/bin/python2.6
Package: gwibber-service 2.29.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with DBusException in call_blocking()
Uname: Linux 2.6.32-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Mahesh Asolkar (asolkar) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Sense Egbert Hofstede (sense) wrote :

I got this as well, but Apport also notifed me of a crash of Desktopcouch -- which wasn't reported because Firefox was loading with this bug report when Apport tried to send the Desktopcouch one. Nevertheless, Gwibber shouldn't crash when Desktopcouch cannot be found.

visibility: private → public
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
tags: added: metabug
tags: added: iso-testing
Revision history for this message
Anthony Hook (anthonyhook) wrote :

This might be related to bug #527520 as they happened at the same time for me.

Revision history for this message
Stewart G. (birbeck) wrote :

Also on 10.04 64-bit

Revision history for this message
kingbob (scott-mcdougall) wrote :

^ Yep same here. 64 bit with Desktopcouch crashing as well.

Revision history for this message
Guillaume Pascal (guigui14100-deactivatedaccount) wrote :

Same Problem in Netbook Edition

Revision history for this message
Casey J Peter (caseyjp1) wrote :

This crash starts a cascade of crashes to gwibber-accounts (x2) as well. Reproducible every time broadcast accounts is selected from the memenu.

This is as of post installation updates including evolution/gwibber/ and the .15 kernel update.

Revision history for this message
George Kontis (giormatsis) wrote :

This is the message in the terminal

** (gwibber:5155): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:5155): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:5155): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
ERROR:dbus.proxies:Introspect error on :1.70:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
INFO:Gwibber GNOME Client:Running from the system path
No dbus monitor yet
Updating...
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 70, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 439, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 28, in __init__
    self.model = gwui.Model()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 43, in __init__
    self.services = json.loads(self.daemon.GetServices())
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Revision history for this message
Omer Akram (om26er) wrote :

I beleive that this bug is caused by bug#521693 once that's fixed this will also be fixed.

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.