touch-packages team mailing list archive

[Tony Espy <1371320@xxxxxxxxxxxxxxxxxx>]

@Chris

So as it's been explained to me, the indicators were designed to crash
and restart.   This bug is less about the specific crash than it is
about the fact that at some point, the restarts quit happening.

@Antti

In my original description I asked the question "are we using upstart"
to res-pawn the indicator if it crashes, or is some other mechanism
used?

Does your proposed fix apply to the crash itself, or the fact that the
indicator wouldn't restart?

-- 
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/1371320

Title:
  Network Indicator crashes and doesn't restart

Status in “indicator-network” package in Ubuntu:
  Triaged
Status in “indicator-network” package in Ubuntu RTM:
  Triaged

Bug description:
  Device/Image: krillin / rtm #44; writable image, test version of
  urfkill w/hybris Wi-Fi mode enabled.

  While testing the new version of urfkill on krillin, I tried to
  reproduce bug #1339794 ( toggling Flight-Mode too fast leads to bad
  things ).  Every so often the menu would flash, which meant the
  indicator crashed, and it would be re-started as expected.

  After doing this for awhile longer, the indicator crashed, and wasn't
  automatically restarted.   I'll attach a screen shot which shows that
  the menu just reads "Empty!", and the output of 'ps -ale' ( run as
  root ) shows no indicator-network process running:

  root@ubuntu-phablet:/home/phablet# ps -ale | grep indica
  0 S 32011  3102  1819  0  80   0 - 13749 poll_s ?        00:00:00 indicator-trans
  0 S 32011  3103  1819  0  80   0 - 11656 poll_s ?        00:00:00 indicator-messa
  0 S 32011  3104  1819  0  80   0 -  9357 poll_s ?        00:00:00 indicator-bluet
  0 S 32011  3106  1819  0  80   0 - 17391 poll_s ?        00:00:00 indicator-locat
  0 S 32011  3107  1819  0  80   0 -  9388 poll_s ?        00:00:46 indicator-power
  0 S 32011  3113  1819  0  80   0 - 33843 poll_s ?        00:00:00 indicator-datet
  0 S 32011  3117  1819  0  80   0 - 29521 poll_s ?        00:00:00 indicator-sound

  There is an uploaded indicator-network crash file in /var/crash,
  however it looks like it's from yesterday.

  I reviewed the syslog, but it looks like it's been size limited so
  there aren't any upstart messages I can see.

  Are you relying on upstart to re-start the indicator when it dies?  If
  you are, you could be hitting upstart's respawn limit.

  Note, I had the screen pinned on via 'powerd-cli screen on', but I
  don't think this would have any effect on the indicator's failure to
  respawn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371320/+subscriptions