Thanks for the detailed analysis Alexandros. I am able to reproduce the issue reliably on my arale, looking into it.
Note that the fact that keepDisplayOn is requested twice is expected: chromium instantiates one PowerSaveBlocker per stream, so for a video with audio, that’s two streams, hence two requests. Perhaps not the most efficient thing to do, but it should be okay as long as the corresponding removeDisplayOnRequest requests are emitted where relevant. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1502145 Title: Apps can keep screen lit permanently Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: rc-proposed, r140, krillin There are times when it seems the display blanking policy stops working and the display stays on until I press the power button. Steps to reproduce: * install and start Siete * put it in background Expected outcome: * the display is switched off after a predetermined amount of time Actual outcome: * the display stays on forever ====== Now that apps can request the screen to stay on, they can do so regardless of whether they're focused/visible or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
