As I said in an other bug report [1], it seems like the couchdb service may go away for some reason (going to sleep seems to trigger this sometimes) and come back listening on a different port. Some debugging in gwibber-service let us see that its desktopcouch.records.server instance still holds the original port number (<OAuthCapableServer 'http://localhost:33312'>).
This means that simply trying to reconnect to the server won't work ; the server is no longer listening on this port. I don't know the internals of desktopcouch well enough to know at which level it should be best to drop the reference to the old server url and get a new one. [1] https://bugs.edge.launchpad.net/gwibber/+bug/523964/comments/32 -- gwibber-service crashed with error in connect() https://bugs.launchpad.net/bugs/522538 You received this bug notification because you are a member of Ubuntu Bug Control, which is a subscriber of a duplicate bug. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
