I can confirm I'm still seeing this bug with gwibber 2.30.0.1-0ubuntu1 and desktopcouch 0.6.4-0ubuntu3.
When I try to start the Gwibber client, I see the following in ~/.cache/gwibber/gwibber.log:
2010-05-16 23:02:40,806 - Gwibber GNOME Client - INFO - Running from the system path
2010-05-16 23:02:41,164 - Gwibber Dispatcher - ERROR - Failed to raise client (DBusException(dbus.String(u'Message did not receive a reply (timeout by message bus)'),),)
I can confirm I'm still seeing this bug with gwibber 2.30.0.1-0ubuntu1 and desktopcouch 0.6.4-0ubuntu3.
When I try to start the Gwibber client, I see the following in ~/.cache/ gwibber/ gwibber. log:
2010-05-16 23:02:40,806 - Gwibber GNOME Client - INFO - Running from the system path dbus.String( u'Message did not receive a reply (timeout by message bus)'),),)
2010-05-16 23:02:41,164 - Gwibber Dispatcher - ERROR - Failed to raise client (DBusException(