This bug was fixed in the package indicator-network - 0.5.1+14.10.20141031.3~rtm-0ubuntu1
--------------- indicator-network (0.5.1+14.10.20141031.3~rtm-0ubuntu1) 14.09; urgency=low [ Jussi Pakkanen ] * Use std::quick_exit. (LP: #1381041) [ Marcus Tomlinson ] * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) [ Antti Kaijanmäki ] * Increase the default timeouts to match industry standards. (LP: #1381041) * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) -- Ubuntu daily release <ps-jenk...@lists.canonical.com> Fri, 31 Oct 2014 14:16:08 +0000 ** Changed in: indicator-network (Ubuntu RTM) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1381041 Title: [TOPBLOCKER] Network indicator is sometimes blank Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-network” source package in Utopic: New Status in “indicator-network” source package in Vivid: Fix Released Status in “indicator-network” package in Ubuntu RTM: Fix Released Bug description: This is on krillin r103, but it has been happening for a while. See attached photo. I am not certain what triggers it. but I think it may happen when wifi APs become in and out of range while walking around town (as if the list does not refresh reliably). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp