Bug 334411 - Screen Energy Saving timeout on dual-monitor system starting one after another with timeout delay
Summary: Screen Energy Saving timeout on dual-monitor system starting one after anothe...
Status: RESOLVED WORKSFORME
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Plasma Development Mailing List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-05-06 11:21 UTC by o_0
Modified: 2018-10-27 02:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description o_0 2014-05-06 11:21:02 UTC
When enabling Screen Energy Saving(System Settings->Power Management->Energy Saving) after a certain timeout(e.g. 10min.) the first monitor is switching off, and onyl then after another 10 min. the second one is  swithing off.

Reproducible: Always

Steps to Reproduce:
1.set timeout 
2.wait timeout
3.wait timeout
Actual Results:  
both monitors are powered down after 2xTimeouts

Expected Results:  
both monitors are powered down after 1xTimeouts

System: Intel(R) Core(TM) i5-3550, FreeBSD 10.0-R amd64, kde-4.12.4, dual-head Intel(R) HD Graphics 2500;
Comment 1 Kai Uwe Broulik 2015-06-07 18:05:12 UTC
Can you check what happens when you run xset dpms force off?
Comment 2 o_0 2015-06-09 14:20:15 UTC
Both monitors are going down.
Comment 3 Andrew Crouthamel 2018-09-25 21:49:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 02:42:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!