https://bugs.kde.org/show_bug.cgi?id=481308
--- Comment #37 from Jakob Petsovits <jpe...@petsovits.com> --- (In reply to Steven Noonan from comment #32) > Tried applying the patch in the powerdevil merge request and > rebuilt/installed poweredevil. From what I can tell it had no impact on > either the escape key behavior or the blank lock screen render. (In reply to Giacomo Lozito from comment #35) > Same, patch does not seem to change behaviour. Also FWIW, I have turn off > screen automatically after 5 mins in Energy Saving config, and allow > unlocking without password for 15 seconds in Screen Locking config. Thanks for testing, much appreciated. I'm unclear as to why the fix wouldn't be working. Given that you have a built-from-souce setup, could you do two more things to help out? 1. Please make sure that $PREFIX/lib/plugins/powerdevil/action/powerdevil_dpmsaction.so was installed in addition to the powerdevil binary itself. That's where the power management service's screen turn-off logic (and the proposed fix) is located in practice. 2. Please provide some of that new debug output that I added in the same commit, to get a rough understanding of how your screen turns blank. On a system with systemd, the easiest way to make the extra logs show up in journalctl is: systemctl edit --user plasma-powerdevil.service and in the free space between the top two comment paragraphs, add this line: [Service] Environment="QT_LOGGING_RULES=org.kde.powerdevil=true" The new logging entries all start with "org.kde.powerdevil: DPMS:", they describe what idle timeouts are set for the action to trigger and when the screen actually gets turned off. Please paste some of those logs here. If that's an issue because the screen is blank, I've found that switching between virtual terminals (e.g. Ctrl+Alt+F7 and back to the original one, wherever it's located as per `loginctl list-sessions`) will restore the screen to non-black. Thanks! -- You are receiving this mail because: You are watching all bug changes.
