I tried to reproduce the bug but can't find the specific program or command to trigger the dialog I saw.
Anyway, messing around a bit, I think this may not related to gwibber, but to the indicator-applet, or any indicator-stuff. By killing indicator-me, the Accounts item in the indicator applet menu disappear, and gwibber only manage *broadcast* accounts, right ? But maybe gwibber is in the same project ? (Social from the start project?) Still, running gwibber or gwibber-preferences, or gwibber-accounts, I still get desktopcouch errors (like in this bug), but apport can't report it because it can't connect to the crash database, even if I'm connected to the Internet and made no network changes whatsoever. I admit this message could be confusing, but if you could point me to resources explaining the relation between gwibber, the indicator applet, or desktopcouch; I would be happy to provide stacktraces and clear and concise bug reports. -- gwibber-accounts crashed with ServerError in _request() https://bugs.launchpad.net/bugs/528286 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
