| Summary: | [bug] Monitor will not go into standby on Weston idle | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | Brian Lovin <brian.j.lovin> |
| Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Brian Lovin
2013-01-30 18:47:04 UTC
How long did you actually wait for monitor to go into standby after going black? Weston has two timeouts, and the idle cycle works like this (or at least should work): 1. wait for the idle timeout to pass (the one set with weston -i option) 2. screen fades to black 3. if screensaver is configured: 3.1. execute weston-screensaver and fade in 3.2. screensaver is displayed until its timeout (weston.ini option screensaver:duration) 3.3. screen fades to black 4. monitor goes off or standby So maybe there is a bug in the logic for the case without a screensaver. I'm not sure if the duration is still required to pass until monitor goes off in the case of no screensaver. Looks like the default duration is 1 min, and the weston.ini example has 10 mins. I have let the application sit over night before, and just did a test where I let it sit for 15 minutes after weston idled out. I do not have a screensaver installed, but the configuration file does have this line: path=/usr/libexec/weston-screensaver Weston prints out that there is no such file. commit 18639f8d4a28b4471516080c7af68926eaeb62e2 Author: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com> Date: Fri Feb 15 18:44:19 2013 +0200 shell: Set the DPMS state if the screensaver fails to launch or dies The lock hook in desktop-shell only changes the DPMS state the second time it is called, because during the first time it launches the screensaver and wakes the compositor again when the screensaver surface is configured. However, if the screensaver fails to launch, the output is left in an enabled state, even thought there's no content being displayed on the screen. Fix this by disabling the outputs when the screensaver dies if the shell is still locked. https://bugs.freedesktop.org/show_bug.cgi?id=60084 Verified fix resolves issue, and closing as verified. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.