Gwibber service in odd state

[Ted Gould]

Binary package hint: gwibber

When I started my machine this moring Gwibber was in an odd state where it wouldn't start the GUI. When starting from the command line I got this:

ted@vee:~$ ps -ef | grep gwibber
ted 9477 1 1 08:38 ? 00:00:01 /usr/bin/python /usr/bin/gwibber-service
ted 9709 1 0 08:38 ? 00:00:00 /usr/bin/python /usr/bin/gwibber
ted 9792 9767 0 08:39 pts/0 00:00:00 grep gwibber
ted@vee:~$ gwibber

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

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

** (gwibber:9796): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Updating...
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 67, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 447, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 29, 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.
ted@vee:~$

When restarting the service Gwibber worked normally.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gwibber 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Wed Jul 14 08:47:29 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gwibber

[Ken VanDine (ken-vandine)]

Thanks for the bug report, but unfortunately there isn't enough information there to determine what actually went wrong. I suspect perhaps a race condition starting the gwibber-service, and one process grabbed the dbus name but wasn't answering on it. But that is just speculation, please re-open if it happens again and we can try to dig deeper.

[Victor Vargas (kamus)]

@Ted, Please could you run in a terminal gwibber-service -d -o and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks!