This issue is related to a number conditions where the indicator may crash. Once the process has crashed beyond its upstart respawn limit, it no longer recovers (hence the empty indicator). I've just linked yet another branch (fix-gmainloop-syncing) that includes some fixes to a number of synchronisation issues that contributed to these crashes.
-- 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
