gwibber crashed with DBusException in call_blocking(): 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.

[Alan Pope 🍺🐧🐱 🦄]

Binary package hint: gwibber

Opened gwibber-service -d in a terminal and gwibber in another, crashage occured.

alan@wopr:~$ gwibber-service -d
Loading plugin Twitter version 1.0
Loading plugin Facebook version 1.1
Loading plugin Identi.ca version 1.1
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 505, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 361, in _handle_results
    cache[job]._set(i, obj)
  File "/usr/lib/python2.7/multiprocessing/pool.py", line 555, in _set
    self._callback(self._value)
  File "/usr/lib/python2.7/dist-packages/gwibber/microblog/dispatcher.py", line 517, in loading_complete
    if len(db.execute("""select * from messages where mid = '%s' and account = '%s' and stream = '%s'""" % (o2[1], o2[2], o2[6])).fetchall()) > 0:
OperationalError: database is locked

ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: 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.
DEBUG:Gwibber Dispatcher:Refresh interval is set to 3
DEBUG:Gwibber Dispatcher:** Starting Refresh - 2011-03-17 13:17:11.57 **

alan@wopr:~$ gwibber -d
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 621, 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: 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.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber 2.91.91.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Mar 17 13:14:18 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/gwibber -d
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
PythonArgs: ['/usr/bin/gwibber', '-d']
SourcePackage: gwibber
Title: gwibber crashed with DBusException in call_blocking(): 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.
UpgradeStatus: Upgraded to natty on 2011-01-19 (57 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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 #700667, 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.

[Ken VanDine (ken-vandine)]

This is not a dupe of bug #700667, so I removed that. This is related doing a vacuum on the database at startup, which was just added recently. We need to move that to a house keeping thread so it happens when nothing is blocked on it.