I tested by reverting the lazy loading branch of unity and they all worked fine. So it was introduced by rev 1133 on trunk.
Without reverting that branch, I do see the following output in .xsession-errors when right-clicking on a lens that isn't loading the sections: (<unknown>:24978): dee-CRITICAL **: dee_model_get_first_iter: assertion `DEE_IS_MODEL (self)' failed (<unknown>:24978): dee-CRITICAL **: dee_model_get_last_iter: assertion `DEE_IS_MODEL (self)' failed I suspect it isn't really lazy loading the sections model, so now it doesn't block on the model being up but never connects when it is available. -- You received this bug notification because you are a member of Gwibber Bug Heros, which is subscribed to Gwibber. https://bugs.launchpad.net/bugs/758839 Title: Lens doesn't start on login Status in A Unity Lens for AskUbuntu.com: Incomplete Status in Gwibber: New Status in Gwibber unity-lens-gwibber series: Confirmed Status in LibUnity: Confirmed Status in Unity: Triaged Status in Unity Books Lens: Confirmed Bug description: I can reproduce this on 2 machines, the lens doesn't start up, but the daemon is running. I have to kill the daemon and then reinitialize unity for it to work. _______________________________________________ Mailing list: https://launchpad.net/~gwibber-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~gwibber-bugs More help : https://help.launchpad.net/ListHelp
