[Active] [Bug 304877] None of the powersaving settings appear to have influence
https://bugs.kde.org/show_bug.cgi?id=304877 Sebastian Kügler se...@kde.org changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||se...@kde.org Resolution|--- |FIXED --- Comment #11 from Sebastian Kügler se...@kde.org --- Confirmed working now. -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 304877] None of the powersaving settings appear to have influence
https://bugs.kde.org/show_bug.cgi?id=304877 --- Comment #8 from Oliver Henshaw oliver.hens...@gmail.com --- (In reply to comment #6) On the Wetab i have to disable power management, so i can work. After an update, screen brightness can go to 100%. After abotu 20 minutes, the screen gets darker and it is no longer possible to change the brightness. Brightness problems are at bug #312579 (In reply to comment #7) I can confirm that on my WeTab. After a while (far less than the 60 minutes shown in Settings), the screen actually goes off and won't turn on again unless you suspend an resume again. Not sure if that's actually a PA problem or maybe a kernel problem. If you can get a konsole up can you tell me the result of 'xset -q' right now, and just after the screen turns off (do 'sleep XX; xset -q' with XX being whatever time it takes for the screen to turn off plus ten seconds). Can you also get the result just before the screen turns off, for completeness? -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 304877] None of the powersaving settings appear to have influence
https://bugs.kde.org/show_bug.cgi?id=304877 --- Comment #9 from Oliver Henshaw oliver.hens...@gmail.com --- Git commit c07f1381545005d64e72e0699c9f0de37b492f62 by Oliver Henshaw. Committed on 25/03/2013 at 17:34. Pushed by oliverhenshaw into branch 'oliverhenshaw/power-timeouts'. Suspend idle timeouts are stored in milliseconds Was storing in centiseconds(?) and in seconds in one place. Meant that suspend was activated much too soon. Suspend timeouts are currently commented out due this problem but should work properly when or if they are re-enabled. Related: bug 310506 M +7-7 applications/settings/modules/powermanagement/contents/ui/Power.qml http://commits.kde.org/plasma-mobile/c07f1381545005d64e72e0699c9f0de37b492f62 -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 304877] None of the powersaving settings appear to have influence
https://bugs.kde.org/show_bug.cgi?id=304877 --- Comment #9 from Oliver Henshaw oliver.hens...@gmail.com --- Git commit c07f1381545005d64e72e0699c9f0de37b492f62 by Oliver Henshaw. Committed on 25/03/2013 at 17:34. Pushed by oliverhenshaw into branch 'oliverhenshaw/power-timeouts'. Suspend idle timeouts are stored in milliseconds Was storing in centiseconds(?) and in seconds in one place. Meant that suspend was activated much too soon. Suspend timeouts are currently commented out due this problem but should work properly when or if they are re-enabled. Related: bug 310506 M +7-7 applications/settings/modules/powermanagement/contents/ui/Power.qml http://commits.kde.org/plasma-mobile/c07f1381545005d64e72e0699c9f0de37b492f62 --- Comment #10 from Oliver Henshaw oliver.hens...@gmail.com --- Git commit 7c33ee0a6d2fa5b92431ad974e512f1b5d978366 by Oliver Henshaw. Committed on 25/03/2013 at 17:21. Pushed by oliverhenshaw into branch 'oliverhenshaw/power-timeouts'. DPMS idle timeouts are stored in seconds Meant that screen power-saving was probably never activated. Related: bug 310506 M +7-7 applications/settings/modules/powermanagement/contents/ui/Power.qml http://commits.kde.org/plasma-mobile/7c33ee0a6d2fa5b92431ad974e512f1b5d978366 -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 304877] None of the powersaving settings appear to have influence
https://bugs.kde.org/show_bug.cgi?id=304877 Thomas Pfeiffer colo...@autistici.org changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Version|PA 3|Master Ever confirmed|0 |1 --- Comment #7 from Thomas Pfeiffer colo...@autistici.org --- I can confirm that on my WeTab. After a while (far less than the 60 minutes shown in Settings), the screen actually goes off and won't turn on again unless you suspend an resume again. Not sure if that's actually a PA problem or maybe a kernel problem. -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
[Active] [Bug 304877] None of the powersaving settings appear to have influence
https://bugs.kde.org/show_bug.cgi?id=304877 Wromey wolfgang.ro...@gmx.net changed: What|Removed |Added CC||wolfgang.ro...@gmx.net --- Comment #6 from Wromey wolfgang.ro...@gmx.net --- On the Wetab i have to disable power management, so i can work. After an update, screen brightness can go to 100%. After abotu 20 minutes, the screen gets darker and it is no longer possible to change the brightness. -- You are receiving this mail because: You are the assignee for the bug. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
