Re-opening powerd task, as OTA3 did *not* solve this problem, and we're
still not sure where the problem lies.

I'm also going to rename the title to "Sometimes need 3 power presses to
turn on screen" because I want to make this bug more obviously distinct
from bug 1421455 and other display bugs.

** Changed in: powerd (Ubuntu)
       Status: Invalid => New

** Summary changed:

- Pressing power button to resume does not turn on screen
+ Sometimes need 3 power button presses to turn on screen

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

Title:
  Sometimes need 3 power button presses to turn on screen

Status in the base for Ubuntu mobile products:
  New
Status in Unity System Compositor:
  New
Status in powerd package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  [filing here although may be other components]

  Mako running 211 from rtm
   I experienced these symptoms which have been previously mitigated in other 
scenarios.
  Last week while traveling and roaming this happened pretty much 100% of the 
time.
  This occurred in all areas (hotel, MWC, outside, etc)

  Press power button, no response
  Press button again, screen turns on for a few seconds then turns off
  Press button again, either phone resumes or more often the power dialog is 
shown

  When I returned back home the function was normal without reboot or
  other changes.

  The differences in environment:
  Roaming on foreign GSM network
  Lots of Wifi APs not connected

  Attached are some perhaps relevant logs, unfortunately the syslog
  rolled.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to