Hi,

I suggest that after you kill gwibber-service and gwibber, you manually start 
*both* of them. Try opening two terminal windows; in the first, run:
gwibber-service -d -o
(That is, debug mode, output to the console/terminal.)

In the second terminal window, after gwibber-service has done its
initial check for updates, you could run gwibber and monitor the logged
messages. I suspect the DBus exceptions will go away once gwibber-
service is running and available for gwibber to connect to. The error
messages from both terminals may provide useful information to you, or
(when you post it here) to Gwibber developers.

Thanks,
Ed.

-- 
Gwibber freezes shortly after start up
https://bugs.launchpad.net/bugs/574480
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to