https://bugs.kde.org/show_bug.cgi?id=481308
--- Comment #38 from Giacomo Lozito <giacomo.loz...@gmail.com> --- (In reply to Jakob Petsovits from comment #37) > (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! Happy to test. For 1. I confirmed that /usr/lib/qt6/plugins/powerdevil/action/powerdevil_dpmsaction.so is included in the arch powerdevil package I patched and rebuilt. I also confirmed its md5sum being different before/after rebuild/reinstall to make sure it's been modified. For 2. I have enabled logging and I can see some of the logging lines in question, more precisely (filtering only the powerdevil: DPMS lines): Mar 09 17:00:20 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 60000ms Mar 09 17:00:22 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 300000ms Mar 09 17:00:39 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 60000ms Mar 09 17:00:43 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 300000ms Mar 09 17:01:23 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 300000ms Mar 09 17:01:20 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 60000ms Mar 09 17:02:13 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 60000ms Mar 09 17:02:25 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 300000ms for each of the 4 attempts, the first line (screen lock activating) pops up as soon as I activate screen lock using Meta+L. The screen unlocked one comes up as I blindly type my password to unlock screen. Worth mentioning that one of these 4 attempts was "successful" (like I mentioned before, rarely the screenlock screen will show as expected). I also tried to switch virtual terminal in the fourth attempt, which causes the screenlock screen to show correctly once switched back to, but does not seem to produce any additional log line of interest. -- You are receiving this mail because: You are watching all bug changes.
