[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #66 from Nate Graham --- There are multiple issues at play. If you're still experiencing some variant of this issue, please open a new bug report instead of commenting on this one. And please be *extremely specific* regarding steps to reproduce so we can distinguish the issues. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #65 from Gabriel Barros --- (In reply to Gabriel Barros from comment #63) > maybe a regression, but now happening on X11 with 6.0.4 > > Was all good under wayland, and ironically, under X11 on 6.0.2! > > Operating System: Arch Linux > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Kernel Version: 6.8.7-arch1-2 (64-bit) > Graphics Processor: AMD Radeon Graphics more details: backlight do turn off when screen locks. moving the mouse turn it on but only show mouse cursor. pressing ESC moves back to screen off. pressing ESC again turns backlight with only mouse cursor again. Sometimes moving to another tty and back shows the image, sometimes it does not. (it seems that changing tty first thing and back, works. but if you cycle ESC then it won't work. but reproduction is not 100%) unlocking by typing password blind or using fingerprint touch do resume image fine on unlocked desktop. regarding the previous comment about > Ironically, this behavior would occur specifically when the DPMS > action (a.k.a. "When locked, turn screen off") was disabled. systems on 6.0.4 do not have this option as they have the new Energy Saving screen design. Maybe those upgraded systems have left over values somewhere? All my 6.0.4 systems on X11 do it immediately without animation! on wayland they respect the timer and show fadeout animation, even if the timer is zero (then it immediately shows the lockscreen and fade it) On both type of systems the setting shows on the UI as "When locked, turn off screen in: after 60 sec" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #64 from firewalker --- For me it was never fixed on X11. Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Gabriel Barros changed: What|Removed |Added CC||descartav...@gmail.com --- Comment #63 from Gabriel Barros --- maybe a regression, but now happening on X11 with 6.0.4 Was all good under wayland, and ironically, under X11 on 6.0.2! Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-2 (64-bit) Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Artem Klevtsov changed: What|Removed |Added CC||a.a.klevt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Michael Hamilton changed: What|Removed |Added CC||mich...@actrix.gen.nz --- Comment #62 from Michael Hamilton --- I saw this happen this evening on 6.0.3 (Tumbleweed 20240328, X11, nvidia 550.54). After returning to my PC, the lock screen was blank, but the arrow cursor was moveable. I used alt-ctrl-f1 to a console and then "loginctl unlock-session N" as a workaround. It seems to be happening about one time in ten. More interestly this also happened to another desktop in the home which is still on KDE5. On this other KDE5 based PC it's been happening much less often, perhaps once a month. Could the origin of this bug be something that has been lurking since KDE5 but changes have now caused it to occur more frequently? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 pmarget...@gmail.com changed: What|Removed |Added CC|pmarget...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #61 from Tony --- (In reply to Jakob Petsovits from comment #60) > Esc in the screen locker is the key assigned to turning the screen off. When > it's already turned off, a second press of Esc or any other key should turn > the screen back on and show the password input field. > > Could you go into detail about how the behavior differs from this expected > behavior on your system? Ideally create a new bug because we don't want this > thread to become a collection for all things related to screens turning off, > just the screen turning off when the screen locker activates. Oh, my bad - I wasn't aware of such behavior. Thanks for the clarification! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #60 from Jakob Petsovits --- (In reply to Tony from comment #59) > Whenever lock screen is triggered and I hit Esc in order to show input > password field - screen becomes black like it used to before mentioned fix. > Happens on latest Plasma 6.0.2 under X11 Esc in the screen locker is the key assigned to turning the screen off. When it's already turned off, a second press of Esc or any other key should turn the screen back on and show the password input field. Could you go into detail about how the behavior differs from this expected behavior on your system? Ideally create a new bug because we don't want this thread to become a collection for all things related to screens turning off, just the screen turning off when the screen locker activates. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Tony changed: What|Removed |Added CC||wladys...@outlook.com --- Comment #59 from Tony --- Whenever lock screen is triggered and I hit Esc in order to show input password field - screen becomes black like it used to before mentioned fix. Happens on latest Plasma 6.0.2 under X11 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added CC||hunterofgy...@gmail.com --- Comment #58 from Nate Graham --- *** Bug 483327 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=483420| -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=483420 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=483371 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added CC||jnoricha...@blueyonder.co.u ||k --- Comment #57 from Nate Graham --- *** Bug 482964 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #56 from rodolfosil...@tutanota.com --- *** Bug 482626 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Jakob Petsovits changed: What|Removed |Added CC||warca...@live.com --- Comment #55 from Jakob Petsovits --- *** Bug 482947 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added Version Fixed In||6.0.2 --- Comment #54 from Nate Graham --- That's different; please open a new bug report for it. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #53 from pmarget...@gmail.com --- Confirming fixed in Plasma 6.0.2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #52 from firewalker --- Some times I am unable to unlock the session. I have to use loginctl from a VT. The screen locker displays just an unlock button that doesn't do anything. Is it related? https://i.imgur.com/XuVBJCn.jpeg https://i.imgur.com/tNbrYJc.jpeg -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nicolas Fella changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/powerdevil/-/commit/be2b |ma/powerdevil/-/commit/a150 |83615d879549ecf9a47b66dc668 |b9fa622b71420d3c231eb87be69 |87419a2dc |5d3f96483 --- Comment #51 from Nicolas Fella --- Git commit a150b9fa622b71420d3c231eb87be695d3f96483 by Nicolas Fella, on behalf of Jakob Petsovits. Committed on 12/03/2024 at 11:15. Pushed by nicolasfella into branch 'Plasma/6.0'. actions/dpms: Ignore turn-off triggers when action is disabled Early Plasma 6.0 releases saw many people reporting unintentional screen turn-off when the screen locker activates/deactivates, and when the system wakes up from sleep. On X11, this was visible to the user immediately, whereas on Wayland it spammed system logs with warnings of invalid -1 idle timeout registrations. Ironically, this behavior would occur specifically when the DPMS action (a.k.a. "When locked, turn screen off") was disabled. The reason is that the DPMS object gets created either way, and sets up its screen locker activation change handler as well as suspend/resume handlers in the constructor. But timeout values can remain invalid until the action is loaded/enabled and timeout values are populated from profile settings. Using invalid timeouts in these handlers caused this headache. This bug was introduced by commit c58085b4, which fixed a bunch of things, bug also removed checks for invalid timeout values. Turns out we still need some kind of checks. We now prevent bad timeout registrations by interpreting negative values in m_idleTimeoutWhenUnlocked as "idle timeout disabled". Checks for this value ensure that registerIdleTimeout() is only called when the action is loaded, regardless of whether it's triggered by screen locker changing its activation status, resume after suspend, or any other event. Alternatively, we could have also moved some signal connections into loadAction() and disconnected them in onProfileUnload(). Checking on every registration call seems more robust though. Related: bug 482077 (cherry picked from commit be2b83615d879549ecf9a47b66dc66887419a2dc) M +24 -10 daemon/actions/bundled/dpms.cpp M +1-0daemon/actions/bundled/dpms.h https://invent.kde.org/plasma/powerdevil/-/commit/a150b9fa622b71420d3c231eb87be695d3f96483 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Jakob Petsovits changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/commit/be2b ||83615d879549ecf9a47b66dc668 ||87419a2dc --- Comment #50 from Jakob Petsovits --- Git commit be2b83615d879549ecf9a47b66dc66887419a2dc by Jakob Petsovits. Committed on 12/03/2024 at 03:47. Pushed by nicolasfella into branch 'master'. actions/dpms: Ignore turn-off triggers when action is disabled Early Plasma 6.0 releases saw many people reporting unintentional screen turn-off when the screen locker activates/deactivates, and when the system wakes up from sleep. On X11, this was visible to the user immediately, whereas on Wayland it spammed system logs with warnings of invalid -1 idle timeout registrations. Ironically, this behavior would occur specifically when the DPMS action (a.k.a. "When locked, turn screen off") was disabled. The reason is that the DPMS object gets created either way, and sets up its screen locker activation change handler as well as suspend/resume handlers in the constructor. But timeout values can remain invalid until the action is loaded/enabled and timeout values are populated from profile settings. Using invalid timeouts in these handlers caused this headache. This bug was introduced by commit c58085b4, which fixed a bunch of things, bug also removed checks for invalid timeout values. Turns out we still need some kind of checks. We now prevent bad timeout registrations by interpreting negative values in m_idleTimeoutWhenUnlocked as "idle timeout disabled". Checks for this value ensure that registerIdleTimeout() is only called when the action is loaded, regardless of whether it's triggered by screen locker changing its activation status, resume after suspend, or any other event. Alternatively, we could have also moved some signal connections into loadAction() and disconnected them in onProfileUnload(). Checking on every registration call seems more robust though. Related: bug 482077 M +24 -10 daemon/actions/bundled/dpms.cpp M +1-0daemon/actions/bundled/dpms.h https://invent.kde.org/plasma/powerdevil/-/commit/be2b83615d879549ecf9a47b66dc66887419a2dc -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 duha.b...@gmail.com changed: What|Removed |Added CC||duha.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nicolas changed: What|Removed |Added CC||nico...@hoeft.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #49 from Giacomo Lozito --- (In reply to Jakob Petsovits from comment #44) > Not sure how best to deal with bug reports because ideally we'd have two > separate ones, but if the symptoms are indeed very similar then it'll be > difficult to tell them apart. Hopefully a large number of users will see > their setup fixed and the remaining ones can target the screen locker / > Plasma theme issue in a targeted way. I have created a separate bug report (https://bugs.kde.org/show_bug.cgi?id=483163) for the breeze style + kscreenlocker issue. Not an urgent one to fix imho as I can simply switch to Breeze Light for now to mitigate issue. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 beloko...@gmail.com changed: What|Removed |Added CC||beloko...@gmail.com --- Comment #48 from beloko...@gmail.com --- I'm having same issue, but I found strange behavior: I have screen edges enabled to show overview. When I lock the screen and blindly enter the password, the screen flashes and turns black again. However, if you move the cursor to the edge, the screen is became visible, but if you exit overview, everything turns black again. This issue only appears in X11. >From "About system": Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450 AORUS M -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Jakob Petsovits changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482077 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #47 from Jakob Petsovits --- (In reply to pmargeti34 from comment #46) > @Jakob Petsovits new piece of info: when "turn off screen" setting in Energy > saving is enabled, screen locking works as intended (meaning no black > screen). I've tried playing with "when locked, turn screen off" values and > it had no effect, even the ones under 15 seconds still didn't manage to > trigger the bug. Is it the same for the others affected? Thank you. This matches what I saw in the code. The bug is caused specifically by the turn-off action *not* being enabled and its settings not being read, but the screen locker activation causes the code to run anyway and uses an invalid (negative, immediate) timeout instead of ignoring the activation. Wake-up from sleep is also affected in the same way. You should be able to avoid this bug by turning on "When locked, turn screen off" with any duration of your choice, until the next release (hopefully) picks up the fix. At that point (hopefully in 6.0.2) disabling the automatic screen turn-off should work again as intended. That's assuming you're not running into any other bugs. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #46 from pmarget...@gmail.com --- @Jakob Petsovits new piece of info: when "turn off screen" setting in Energy saving is enabled, screen locking works as intended (meaning no black screen). I've tried playing with "when locked, turn screen off" values and it had no effect, even the ones under 15 seconds still didn't manage to trigger the bug. Is it the same for the others affected? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #45 from rodolfosil...@tutanota.com --- I have not yet applied the patch,b ut added the debug clause to systemd unit. This happend when locking, then waiting some time, switching VT switiching back. Mar 09 19:58:54 host1 systemd[1695]: Started Powerdevil. Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Currently using activity "f99da2dc-b775-44af-b39d-950ba2bff747" Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Settings for loaded activity: Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: "InhibitScreenManagement" = QVariant(bool, false) Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: "InhibitSuspend" = QVariant(bool, false) Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Loading profile for plugged AC Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Handle button events action could not check for screen configuration Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Can't contact ck Mar 09 19:58:54 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Charge thresholds: start at 0 - stop at 100 Mar 09 19:59:00 host1 plasmashell[2330]: org.kde.plasma.nm.libs: Wireless scan on "wlp4s0" failed: "Scanning not allowed while unavailable" Mar 09 19:59:04 host1 systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@7.service: Deactivated successfully. Mar 09 19:59:04 host1 systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@1.service: Deactivated successfully. Mar 09 19:59:04 host1 systemd[1]: dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@2.service: Deactivated successfully. Mar 09 19:59:04 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 0 Mar 09 19:59:06 host1 kscreenlocker_greet[87458]: pam_warn(kde-smartcard:auth): function=[pam_sm_authenticate] flags=0 service=[kde-smartcard] terminal=[] user=[11] ruser=[] rhost=[] Mar 09 19:59:06 host1 kscreenlocker_greet[87458]: pam_warn(kde-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[kde-fingerprint] terminal=[] user=[11] ruser=[] rhost=[] Mar 09 19:59:10 host1 plasmashell[2330]: org.kde.plasma.nm.libs: Wireless scan on "wlp4s0" failed: "Scanning not allowed while unavailable" Mar 09 19:59:10 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 0 Mar 09 19:59:11 host1 /usr/lib/gdm-x-session[1866]: (EE) event6 - Logitech USB-PS/2 Optical Mouse: client bug: event processing lagging behind by 1033ms, your system is too slow Mar 09 19:59:12 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 0 Mar 09 19:59:12 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Keyboard brightness changed!! Mar 09 19:59:12 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value max: 2 Mar 09 19:59:12 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Keyboard brightness changed!! Mar 09 19:59:12 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value max: 2 Mar 09 19:59:15 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 2 Mar 09 19:59:15 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Can't contact ck Mar 09 19:59:15 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: set kbd backlight value: 0 Mar 09 19:59:15 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 0 Mar 09 19:59:15 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Keyboard brightness changed!! Mar 09 19:59:15 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value max: 2 Mar 09 19:59:16 host1 root[87508]: ACPI group/action undefined: button/kpenter / KPENTER Mar 09 19:59:16 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Can't contact ck Mar 09 19:59:16 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: set kbd backlight value: 2 Mar 09 19:59:16 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 2 Mar 09 19:59:16 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Keyboard brightness changed!! Mar 09 19:59:16 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value max: 2 Mar 09 19:59:17 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 2 Mar 09 19:59:17 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Can't contact ck Mar 09 19:59:17 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: set kbd backlight value: 0 Mar 09 19:59:17 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value: 0 Mar 09 19:59:17 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Keyboard brightness changed!! Mar 09 19:59:17 host1 org_kde_powerdevil[87407]: org.kde.powerdevil: Kbd backlight brightness value max: 2 Mar 09 19:59:18 host1
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #44 from Jakob Petsovits --- (In reply to Giacomo Lozito from comment #43) > (In reply to Jakob Petsovits from comment #42) > > (In reply to Giacomo Lozito from comment #41) > > > Based on logs, I think you are right on Powerdevil is not turning the > > > screen > > > off. But something is causing the screen lock not to be displayed (as if > > > its > > > window wasn't drawn?) > > > > Okay, so then we've got two different bugs on our hands. My patch from > > https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 should solve > > one. We'll still have to figure out where the other one comes from. > > For my specific issue, I just made some progress. I tried changing the > plasma style away from breeze to breeze light and now the screen lock > consistently shows up when I lock screen. Once I switch plasma style back to > breeze, I can reproduce the issue again. Switching away from breeze to > breeze dark or oxygen also fixes it. I have tried deleting ~/.cache on the > off chance this is caused by a cached copy of breeze, but does not seem to > help. Interesting. I tried switching between Breeze and Breeze Light, which on my dev session setup doesn't make any difference for the screen locker in that way. Great find though! And this also supports the theory of this "second" issue to be an issue with drawing the screen locker window as opposed to the KWin fade-out effect being inappropriately applied. Not sure how best to deal with bug reports because ideally we'd have two separate ones, but if the symptoms are indeed very similar then it'll be difficult to tell them apart. Hopefully a large number of users will see their setup fixed and the remaining ones can target the screen locker / Plasma theme issue in a targeted way. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 breakingsp...@gmail.com changed: What|Removed |Added CC||breakingsp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #43 from Giacomo Lozito --- (In reply to Jakob Petsovits from comment #42) > (In reply to Giacomo Lozito from comment #41) > > Based on logs, I think you are right on Powerdevil is not turning the screen > > off. But something is causing the screen lock not to be displayed (as if its > > window wasn't drawn?) > > Okay, so then we've got two different bugs on our hands. My patch from > https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 should solve > one. We'll still have to figure out where the other one comes from. For my specific issue, I just made some progress. I tried changing the plasma style away from breeze to breeze light and now the screen lock consistently shows up when I lock screen. Once I switch plasma style back to breeze, I can reproduce the issue again. Switching away from breeze to breeze dark or oxygen also fixes it. I have tried deleting ~/.cache on the off chance this is caused by a cached copy of breeze, but does not seem to help. Anyway, even though this issue only manifests with the screen lock (and the symptoms are deceptively similar to what reported by others for powerdevil) my issue is unrelated with powerdevil. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #42 from Jakob Petsovits --- (In reply to Giacomo Lozito from comment #41) > Based on logs, I think you are right on Powerdevil is not turning the screen > off. But something is causing the screen lock not to be displayed (as if its > window wasn't drawn?) Okay, so then we've got two different bugs on our hands. My patch from https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 should solve one. We'll still have to figure out where the other one comes from. (In reply to Giacomo Lozito from comment #41) > There is an important detail here, which I reported incorrectly in my > previous message, sorry. When I activate the screen lock, the screen goes > blank, but not off (meaning that I can still see the screen backlight on, > and the mouse cursor is visible if I move it). Right, thanks for pointing that out. Those are indeed different things, although I can only see the fade-out effect used by PowerDevil and nothing else (it sets a "_KDE_KWIN_KSCREEN_SUPPORT" atom for X11, implemented in KWin's KscreenEffect). The effect itself also triggers when a display is "aboutToTurnOff", which could be worth exploring too but seems somewhat unlikely. At this point I wonder if there's maybe a second powerdevil running (for a different logged-in Plasma session?) with the old, unfixed code that still manages to activate the fade-out effect but doesn't manage to turn off the display. I wouldn't bet on it, but what other leads do we have at this point? If it's the screen locker window not being drawn, the black screen (with visible cursor) should go away once you blindly unlock the session with your password. The fade-out effect hits all windows, whereas the screen locker on X11 is only a single window that sits on top of all the rest. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #41 from Giacomo Lozito --- > On that note, perhaps run a quick test with powerdevil stopped (i.e. > `systemctl stop --user plasma-powerdevil.service`) to confirm that the DPMS > action is actually responsible for this? Screen stays on with powerdevil > stopped and turns blank with powerdevil running, yes? Just done this test. The screen still goes blank as soon as I activate screen lock, even with powerdevil off, and obviously no powerdevil-related log lines appearing in journalctl. > If you're not seeing those, I have to wonder if perhaps some other component > is independently turning off the screen that's unrelated to PowerDevil. There is an important detail here, which I reported incorrectly in my previous message, sorry. When I activate the screen lock, the screen goes blank, but not off (meaning that I can still see the screen backlight on, and the mouse cursor is visible if I move it). If I then press Esc, it goes off. If I press it again, the screen turns on (with nothing displayed, but the backlight is on) for a moment, then back off. Based on logs, I think you are right on Powerdevil is not turning the screen off. But something is causing the screen lock not to be displayed (as if its window wasn't drawn?) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #40 from Jakob Petsovits --- (In reply to Giacomo Lozito from comment #39) > Note: reading those log lines and looking at where those are located in the > patch, the impression I get is that my timeout for turning off the screen > (60 seconds) is not being honored. Instead, it immediately proceeds to turn > off the screen. This would also explain why I pressing esc turns on the > screen for a moment for me, and then turns it off again (because instead of > waiting 60 seconds, it's doing the fast display turn off without waiting for > timeout). Thanks for the logs. What I'm noticing here is the lack of log messages for when the screen actually *does* get turned off. That would look something like: org.kde.powerdevil: DPMS: starting to fade out org.kde.powerdevil: DPMS: triggered on idle timeout, turning off display and keyboard backlight or perhaps org.kde.powerdevil: DPMS: DPMS: triggered from externally, type: "TurnOff" If you're not seeing those, I have to wonder if perhaps some other component is independently turning off the screen that's unrelated to PowerDevil. (I also just noticed that I forgot adding a similar log entry to the third turn-off call, which should only get triggered if you assign and press the "Turn Off Screen" global keyboard shortcut.) Although in my collection of Plasma source directories, the only other component I see that's calling KScreen::Dpms::switchMode (with Off parameter) is the screen locker in its Esc key handler. I figure that's not getting in the way here. On that note, perhaps run a quick test with powerdevil stopped (i.e. `systemctl stop --user plasma-powerdevil.service`) to confirm that the DPMS action is actually responsible for this? Screen stays on with powerdevil stopped and turns blank with powerdevil running, yes? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #39 from Giacomo Lozito --- Note: reading those log lines and looking at where those are located in the patch, the impression I get is that my timeout for turning off the screen (60 seconds) is not being honored. Instead, it immediately proceeds to turn off the screen. This would also explain why I pressing esc turns on the screen for a moment for me, and then turns it off again (because instead of waiting 60 seconds, it's doing the fast display turn off without waiting for timeout). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #38 from Giacomo Lozito --- (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 6ms Mar 09 17:00:22 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms Mar 09 17:00:39 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 6ms Mar 09 17:00:43 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms Mar 09 17:01:23 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms Mar 09 17:01:20 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 6ms Mar 09 17:02:13 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen lock activating) after 6ms Mar 09 17:02:25 arcadia org_kde_powerdevil[1211]: org.kde.powerdevil: DPMS: registering idle timeout (screen unlocked) after 30ms 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.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #37 from Jakob Petsovits --- (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.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 firewalker changed: What|Removed |Added CC||firew4l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #36 from Nelson --- (In reply to Luke from comment #33) > (In reply to Bug Janitor Service from comment #31) > > A possibly relevant merge request was started @ > > https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 > > Following the logic of this merge request, I was able to fix the problem on > my PC by: > - enabling automatic screen turn-off; > - setting a long-enough LockGrace period. > In my case, LockGrace has to be at least 15 seconds; as soon as it’s set > lower, the unintentional screen turn-off happens again. Can confirm that this setting works. At 15 seconds or more the expected behavior comes back, seeing the lock screen and the screen does not turn off either when locking nor unlocking. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #35 from Giacomo Lozito --- (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. 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. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Kevin Scholey changed: What|Removed |Added CC||kev...@ezeedsl.co.uk --- Comment #34 from Kevin Scholey --- Thanks Luke, That fixed mine as well. Just wait now for an update to PowerDevil KS -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #33 from Luke --- (In reply to Bug Janitor Service from comment #31) > A possibly relevant merge request was started @ > https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 Following the logic of this merge request, I was able to fix the problem on my PC by: - enabling automatic screen turn-off; - setting a long-enough LockGrace period. In my case, LockGrace has to be at least 15 seconds; as soon as it’s set lower, the unintentional screen turn-off happens again. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #32 from Steven Noonan --- 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. I notice that when I get the black screen with mouse cursor, I can move the mouse over where the password field should be and it turns into the I-beam cursor, and I am able to type in the field and unlock the screen. Doing so causes it to present a few frames of what the locker *should* have been rendering before the locker exits. And I can run `kscreenlocker_greet --test` (or without `--test`) and it renders fine, so I'm not sure exactly what is causing it to render the black screen. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=482772| -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482751 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #31 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Steven Noonan changed: What|Removed |Added CC||ste...@uplinklabs.net -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 Jakob Petsovits changed: What|Removed |Added Assignee|plasma-b...@kde.org |jpe...@petsovits.com CC||m...@ratijas.tk, ||natalie_clar...@yahoo.de Component|general |general Product|kscreenlocker |Powerdevil Version|5.93.0 |6.0.1 --- Comment #30 from Jakob Petsovits --- Vlad from the KWin team found the cause of the bug and I can reproduce it now. Working on a fix. And yes, it's my fault. Sorry everyone! -- You are receiving this mail because: You are watching all bug changes.
