I encountered similar phenomena. Yesterday, I deleted my GNOME keyring files (~/.gnome2/keyrings/*.keyring) to avoid annoying password entry message appearing upon startup. Far from my purpose, gwibber went very unstable since then. Sometimes, gwibber didn't display any timeline and Me Menu are trying to create "default.keyring" (here, default is in Japanese ... as I am using ja_JP.UTF8 locale). I found re-creation of key (by "encryption and key files" from Application Menu) and added my Twitter account and password. It seemed problem solved, but in this time, gwibber would not update timeline after about 20 minutes from launch.
After several trial, I found current and tentative solution. It is very simple. * If I found gwibber no longer updates timeline, Close gwibber. * Kill gwibber-service by ps aux | grep gwi kill -KILL (process number of gwibber-service) * restarting gwibber-service by /usr/bin/python /usr/bin/gwibber-service & Currently it works anyway. But I need some essential solution. I suppose this bug is related with python and dbus connection, not authentication module. Hope this helps. -- After adding an account to Gwibber, the "social bar" appears in the Ubuntu Lucid Me Menu; after reboot the social bar/box disappears https://bugs.launchpad.net/bugs/578485 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
