touch-packages team mailing list archive

[Marcus Tomlinson <marcus.tomlinson@xxxxxxxxxxxxx>]

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
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:
  In Progress
Status in “indicator-network” source package in Utopic:
  New
Status in “indicator-network” source package in Vivid:
  In Progress
Status in “indicator-network” package in Ubuntu RTM:
  In Progress

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