This bug was fixed in the package indicator-network -
0.5.1+15.04.20141103-0ubuntu1
---------------
indicator-network (0.5.1+15.04.20141103-0ubuntu1) vivid; urgency=low
[ CI bot ]
* Resync trunk
[ 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)
indicator-network (0.5.1+14.10.20141015-0ubuntu1) 14.09; urgency=low
[ Antti Kaijanmäki ]
* deadlock if calling unlock() inside ready signal for a modem that
does not require unlocking. (LP: #1333121)
-- Ubuntu daily release <[email protected]> Mon, 03 Nov 2014
11:48:11 +0000
** Changed in: indicator-network (Ubuntu Vivid)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381041
Title:
[TOPBLOCKER] Network indicator is sometimes blank
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381041/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
