The same issue for me :
$ gwibber
** (gwibber:4074): WARNING **: Trying to register gtype
'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:4074): WARNING **: Trying to register gtype
'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:4074): WARNING **: Trying to register gtype
'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Removing stale, deceptive pid file.
Apache CouchDB has started, time to relax.
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
Browse your desktop CouchDB at
file:///home/agnes/.local/share/desktop-couch/couchdb.html
No dbus monitor yet
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.
I was re-installed gwibber, unistaller Ubuntu One and I have another issue :
when lauching Gwibber, it's starting the Bean process It's take 100% CPU!
What a shame!
--
Gwibber crash on startup, KeyError: 'doc
https://bugs.launchpad.net/bugs/579668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
