← Back to team overview

touch-packages team mailing list archive

[Bug 1429887] Re: Sometimes need 3 power button presses to turn on screen

 

I'm beginning to doubt that this is particularly associated with system
load (there was speculation that this is related to the scenario of wifi
APs causing NetworkManager and dbus-daemon to go crazy, slowing down the
system, which is a separate bug).

I've used the following script in /etc/init/load.conf to simulate heavy
system load:

description "load"
manual
script
 while true; do true; done &
 while true; do true; done &
 while true; do true; done &
 while true; do true; done &
 while true; do true; done &
 exec cpulimit -l 1 -c 1 -p `ps ax | grep dbus-daemon | head -n 1 | awk '{print $1;}'`
end script

And it definitely slows things down.  But I couldn't reproduce this
specific bug with that running.  I actually haven't seen it at all on my
test or daily driver devices since OTA7.  I don't know if that means it
is fixed, harder to reproduce, or I've just been lucky.

Ari, you mention seeing this a lot.  Are you on OTA7?

-- 
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 Canonical System Image:
  Incomplete
Status in Unity System Compositor:
  New
Status in powerd package in Ubuntu:
  Confirmed
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


Follow ups

References