Gwibber crashes on launch with dbus error

Bug #526060 reported by Mackenzie Morgan
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Undecided
Unassigned

Bug Description

Gwibber from the gwibber-daily PPA, updated today. I'm running Kubuntu Karmic with KDE SC 4.4 (so, same KDE version as Lucid). Should point out that I've yet to have the "new" Gwibber work on KDE.

$ gwibber

** (gwibber:3648): WARNING **: Trying to register gtype 'WnckWindowState' as flags when in fact it is of type 'GEnum'

** (gwibber:3648): WARNING **: Trying to register gtype 'WnckWindowActions' as flags when in fact it is of type 'GEnum'

** (gwibber:3648): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum'
ERROR:dbus.proxies:Introspect error on :1.111:/: 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 36, in <module>
    cdb.getPort()
  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.ServiceUnknown: The name :1.111 was not provided by any .service files

description: updated
Revision history for this message
Mackenzie Morgan (maco.m) wrote :

Fixed in today's daily.

Changed in gwibber:
status: New → Fix Committed
Changed in gwibber:
status: Fix Committed → Fix Released
Revision history for this message
Nick Campbell (ncb000gt) wrote :

I am having this issue with 2.30.0.1 and trunk.

I recently was running Kubuntu and not using Gwibber. But, I changed over to Ubuntu/Gnome, with the Lucid release, and thought I'd try out Gwibber. So, both sets of libraries are on my machine.

Revision history for this message
Nick Campbell (ncb000gt) wrote :

I'm sorry, I just reread the errors and it looks a touch different. I can post a new ticket for it if I can't find a resolution somewhere.

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.