gwibber crashed with DBusException in call_blocking() on startup

Bug #700667 reported by Gary M
640
This bug affects 78 people
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
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
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
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_NZ.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with DBusException in call_blocking()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Gary M (garym) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

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.

tags: removed: need-duplicate-check
tags: added: regression-retracer
Omer Akram (om26er)
visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

Gary, maybe you should leave a message in bug 628686 about it

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
tags: added: bugpattern-needed
Revision history for this message
Victor Vargas (kamus) wrote :

KenVandine had marked this issue as triaged and was assigned to him in another report, however apport marked this one like the source.

Changed in gwibber (Ubuntu):
status: New → Triaged
Victor Vargas (kamus)
Changed in gwibber (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
Revision history for this message
aj00200 (aj00200) wrote :

I previously had the first listed traceback as output, then I installed the latest version of Gwibber from the stable PPA. I am not getting the attached output and Gwibber fails to open an interface, however, the gwibber-service process seems to continue running.

Revision history for this message
Kate Stewart (kate.stewart) wrote :

Based on the number of duplicates, uping the prioirty to high.

Changed in gwibber (Ubuntu):
importance: Medium → High
Revision history for this message
Ken VanDine (ken-vandine) wrote :

@aj00200: are you still getting this same problem? Or perhaps you had upgraded gwibber and the gwibber-service hadn't restarted since the upgrade?

Your particular traceback looks like the gwibber-service process you had running was from 2.32 and the client was 3.0. If you are still getting this same error, please open a new bug for it.

Revision history for this message
Jim Campbell (jwcampbell) wrote :

I am no longer experiencing this problem.
gwibber 3.0.0.1-0ubuntu2
gwibber-service 3.0.0.1-0ubuntu2

Thanks, Ken!

Revision history for this message
Biafra (paulo-a-ferreira) wrote :

Hi,

I'm still with this issue. It started after upgrading to 11.04.

$ gwibber
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 87, in <module>
    client.Client()
  File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 623, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 71, in __init__
    self.setup_ui()
  File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 251, in setup_ui
    self.stream_view.set_state(streams)
  File "/usr/lib/python2.7/dist-packages/gwibber/gwui.py", line 410, in set_state
    self.update()
  File "/usr/lib/python2.7/dist-packages/gwibber/gwui.py", line 397, in update
    self.messages.update(self.navigation.selected_stream)
  File "/usr/lib/python2.7/dist-packages/gwibber/gwui.py", line 751, in update
    self.messages = self.message_view.render([selected_stream], count)
  File "/usr/lib/python2.7/dist-packages/gwibber/gwui.py", line 774, in render
    msgs = json.loads(self.model.streams.Messages(streams[0]["stream"] or "all", streams[0]["account"] or "all", time, streams[0]["transient"] or "0", streams[0].has_key("recipient") and streams[0]["recipient"] or "0", orderby, order, limit))
  File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.7/dbus/connection.py", line 630, 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.

gwibber 3.0.0.1-0ubuntu3
gwibber-service 3.0.0.1-0ubuntu3

The service seams to be running:

$ ps axf|grep gwi
 8522 pts/3 S+ 0:00 | \_ grep --color=auto gwi
 8090 ? SLl 2:03 /usr/bin/python /usr/bin/gwibber-service
 8101 ? S 0:00 \_ /usr/bin/python /usr/bin/gwibber-service
 8102 ? S 0:00 \_ /usr/bin/python /usr/bin/gwibber-service

What kind of debug should I do to help ?

Revision history for this message
adil benseddik (adil-benseddik) wrote :

did you try creating a new user and testing gwibber after that.. it may tell if it's coming from your configuration or from the software.. ??

Revision history for this message
Biafra (paulo-a-ferreira) wrote :

Adil,

Just created a new user and tried it again from commmand line:

gteste@ankh-morpork:~$ gwibber
ERROR:dbus.proxies:Introspect error on com.Gwibber.Service:/com/gwibber/Service: 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.
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 87, in <module>
    client.Client()
  File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 623, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 40, in __init__
    self.model = gwui.Model()
  File "/usr/lib/python2.7/dist-packages/gwibber/gwui.py", line 50, in __init__
    self.services = json.loads(self.daemon.GetServices())
  File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.7/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.7/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
gteste@ankh-morpork:~$

Revision history for this message
adil benseddik (adil-benseddik) wrote :

same here..

Revision history for this message
tqft (ianburrows-au) wrote :

Was working and then a few days ago couldn't restart it after a reboot

ian@tqft:~$ gwibber
ERROR:dbus.proxies:Introspect error on com.Gwibber.Service:/com/gwibber/Service: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 72, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 548, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 34, in __init__
    self.model = gwui.Model()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 42, 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: Message did not receive a reply (timeout by message bus)
Exception AttributeError: "'NoneType' object has no attribute 'px_proxy_factory_free'" in <bound method ProxyFactory.__del__ of <libproxy.ProxyFactory object at 0x92ad50c>> ignored
ian@tqft:~$ gwibber
ERROR:dbus.proxies:Introspect error on com.Gwibber.Service:/com/gwibber/Service: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 72, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 548, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 34, in __init__
    self.model = gwui.Model()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 42, 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: Message did not receive a reply (timeout by message bus)
Exception AttributeError: "'NoneType' object has no attribute 'px_proxy_factory_free'" in <bound method ProxyFactory.__del__ of <libproxy.ProxyFactory object at 0x984d50c>> ignored

Revision history for this message
adil benseddik (adil-benseddik) wrote :

any new.. ??

Revision history for this message
Ken VanDine (ken-vandine) wrote :

Unfortunately this traceback is very generic, so everyone commenting here are likely experiencing different bugs. Anyone affected, please open new bug reports and attach the output of this command:

killall -9 gwibber-service; gwibber-service -do

Changed in gwibber:
status: New → Invalid
Changed in gwibber (Ubuntu):
status: Triaged → Invalid
Revision history for this message
adil benseddik (adil-benseddik) wrote :

yey.. it's done..

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.