Comment 16 for bug 519444
Revision history for this message
| Rick Spencer (rick-rickspencer3) wrote | #16 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I experienced this error under the following conditions:
Just rebooted from a dist-upgrade.
Launched gwibber from the message menu rather than waiting for it to auto-spawn.
The result was that gwibber service did appear to run, as notify-osd was displaying messages, but the gwibber client did not run.