touch-packages team mailing list archive

[Michael Zanetti <michael.zanetti@xxxxxxxxxxxxx>]

** Branch linked: lp:~unity-team/unity8/rtm-20150121

** Changed in: unity8 (Ubuntu RTM)
       Status: New => In Progress

** Changed in: unity8 (Ubuntu RTM)
     Assignee: (unassigned) => Michael Zanetti (mzanetti)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1410830

Title:
  Shutdown dialog appears on resume, after a long delay in screen
  turning on

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  Sometimes, if you press the power button to resume your device, the
  screen will stay black for a long time.  When it does come on again,
  the shutdown dialog is likely showing instead of the greeter.

  You might press the power button again while the screen is black,
  thinking you didn't actually press it the first time.  This will
  immediately turn the screen on and then off again.  At which point a
  third power button press will turn the screen on for good.

  This bug is very similar to bug 1383277 (fixed), which involves a
  shutdown dialog appearing on resume, but for a different reason.  This
  is also very similar to (and may be a dup of) bug 1409003.  But since
  bug 1409003 currently involves an incoming text and this bug does not,
  I'm treating them as separate for now.

  This bug is hard to reproduce.  It seems to involve leaving and
  entering wifi/3G zones (or maybe simply toggling the wifi indicator
  button).  But no reliable steps have been recorded yet.

  I'm guessing that like bug 1383277, it involves some resume-event
  handler blocking the input stack so that Qt doesn't notice the power-
  button-release event.  And since it takes so long to resume, Qt thinks
  the user held down the power button long enough to trigger the
  shutdown dialog.

  A trivial band-aid for this is to not start the shutdown-dialog timer
  if the screen is off.  But that wouldn't address the source cause of a
  blocking event handler.  So I think this still merits investigation.
  But if this is a critical/time-sensitive bug, we could slap a band-aid
  on it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410830/+subscriptions