[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #18 from Zamundaaa --- Git commit 9c049c724e239e68a6466468f8a8e3a2fd4e9402 by Xaver Hugl. Committed on 02/03/2026 at 14:30. Pushed by zamundaaa into branch 'master'. wayland_server: handle suspend inhibition for kscreenlocker too Each process can only have one inhibition at a time, so if KWin and kscreenlocker both delay suspend, one of their requests fails. This instead puts the inhibition file descriptor into a shared_ptr and shares it between workspace and the screenlocker. Related: bug 513150 M +1-1src/core/session.h M +8-4src/core/session_consolekit.cpp M +2-1src/core/session_consolekit.h M +8-4src/core/session_logind.cpp M +2-1src/core/session_logind.h M +2-2src/core/session_noop.cpp M +1-1src/core/session_noop.h M +10 -0src/wayland_server.cpp M +2-0src/wayland_server.h M +1-1src/workspace.h https://invent.kde.org/plasma/kwin/-/commit/9c049c724e239e68a6466468f8a8e3a2fd4e9402 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Nate Graham changed: What|Removed |Added Version|6.6.0 |6.6.2 Fixed/Implemented|| In|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Zamundaaa changed: What|Removed |Added Version|6.6.1 |6.6.0 Fixed/Implemented|| In|| Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/f0f00551a4 ||0ec071095c7f3076221d898ffb9 ||5af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #17 from Zamundaaa --- Git commit fc0f321f15544c80a953bff47d105c8113e317a0 by Xaver Hugl. Committed on 27/02/2026 at 00:26. Pushed by zamundaaa into branch 'master'. backends/drm: reject output configurations when the DrmGpu isn't active We can be certain it won't work, so there's no point in trying. It just results in "permission denied" warnings and nothing useful. M +3-0src/backends/drm/drm_backend.cpp M +1-0src/effect/globals.h M +3-0src/wayland/outputmanagement_v2.cpp M +3-0src/workspace.cpp https://invent.kde.org/plasma/kwin/-/commit/fc0f321f15544c80a953bff47d105c8113e317a0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Nate Graham changed: What|Removed |Added Version||6.6.1 Fixed/Implemented|| In|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Zamundaaa changed: What|Removed |Added CC||[email protected] ||m --- Comment #15 from Zamundaaa --- *** Bug 58 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Zamundaaa changed: What|Removed |Added CC||[email protected] --- Comment #16 from Zamundaaa --- *** Bug 513150 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Zamundaaa changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #14 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/8873 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #13 from Zamundaaa --- https://invent.kde.org/plasma/kwin/-/merge_requests/8282 made a bunch of dpms things more robust, and while I didn't think about it at the time, it does fix this too - when applying dpms changes fails, on the next event related to outputs (like switching VTs) it just tries again. The MR that's still open will make most of the permission warnings go away, a much smaller change should remove the rest of them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #12 from Frederick Zhang --- Ah sorry, my Qt was last upgraded before 15 Feb too. So it's just Frameworks that were upgrade on 15 Feb night right after the last 'Setting dpms mode failed!' log, and Plasma that was upgrade on 18 Feb. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #11 from Frederick Zhang --- It seems the issue has been fixed somehow, although the two MRs are still open. I tested both internal screen + battery and external displays + charger, and it lit up just fine after a single key press or WoL. I did a quick search `journalctl --since 2026-02-06 --grep 'dpms mode failed'` and the last hit was on 15 Feb. Both systemd and nvidia-utils were last upgraded before this. I still see 'Atomic modeset test failed! Permission denied' logs though. I'm not exactly sure what changed. I didn't touch any relevant configurations so it's probably one of the package upgrades, and the only major upgrades I got after 15 Feb were the KDE/Qt ones. KDE Plasma Version: 6.6.0 KDE Frameworks Version: 6.23.0 Qt Version: 6.10.2 Kernel Version: 6.18.9-arch1-2 (64-bit) Graphics Platform: Wayland Were there any other patches that could have fixed this potentially? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 TraceyC changed: What|Removed |Added CC||[email protected] --- Comment #10 from TraceyC --- *** Bug 516038 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 postix changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/8776 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Nate Graham changed: What|Removed |Added CC||[email protected] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Zamundaaa changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #8 from Zamundaaa --- Okay. So then we can be certain that > [ 110.245823] nvidia :01:00.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2467, dev=0xe200, auth=1, DRM_IOCTL_DROP_MASTER + > [ 110.245919] i915 :00:02.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2467, dev=0xe201, auth=1, DRM_IOCTL_DROP_MASTER is from something else. I looked through logind code, and it only calls this when the session is paused, iow when a VT switch happens. I did some more digging, and the nvidia driver's sleep handling script (/usr/bin/nvidia-sleep.sh) does a VT switch before suspend, and switches back after wakeup only after doing some tasks in the driver. I'm quite unhappy about that situation, but assuming that delaying suspend also delays that script, we should be able to deal with it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #7 from Frederick Zhang --- Created attachment 189316 --> https://bugs.kde.org/attachment.cgi?id=189316&action=edit DRM debug log after disabling lact. Captured when using external displays > Can you try removing lact and check if it still happens then? Sure thing. I disabled lact and rebooted my laptop just in case. But unfortunately I still had the issue. By the way I noticed that there were 'Atomic modeset test failed! Permission denied' logs when it was entering sleep state too (so were there last time when I had lact on). journalctl context when entering sleep state: > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Device > /dev/i2c-14 lacks R/W permissions > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Device > /dev/i2c-15 lacks R/W permissions > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Device > /dev/i2c-16 lacks R/W permissions > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Device > /dev/i2c-17 lacks R/W permissions > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Removing > connected display on bus 9 > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] > (dw_remove_display_by_businfo) No Display_Ref found for i2c bus: 9 > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Removing > connected display on bus 16 > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Emitting > DDCA_Display_Status_Event[ 61.292: DDCA_EVENT_DISPLAY_DISCONNECTED, > card0-HDMI-A-2, dref: DDCA_Display_Ref[2], io_path:/dev/i2c-16, ddc working: > false] > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Starting 1 > callback threads > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] libddcutil > callback thread 0x7fee10016f40 started > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Started 1 event > callback thread(s) > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Removing > connected display on bus 17 > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Emitting > DDCA_Display_Status_Event[ 61.292: DDCA_EVENT_DISPLAY_DISCONNECTED, > card0-DP-6, dref: DDCA_Display_Ref[3], io_path:/dev/i2c-17, ddc working: > false] > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Starting 1 > callback threads > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 6063] Invoking callback > function 0x7fee497c57f0 for event DDCA_Display_Status_Event[ 61.292: > DDCA_EVENT_DISPLAY_DISCONNECTED, card0-HDMI-A-2, dref: DDCA_Display_Ref[2], > io_path:/dev/i2c > -16, ddc working: false] in this thread [ 6063] > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 6063] Callback function > 0x7fee497c57f0 for event DDCA_Display_Status_Event[ 61.292: > DDCA_EVENT_DISPLAY_DISCONNECTED, card0-HDMI-A-2, dref: DDCA_Display_Ref[2], > io_path:/dev/i2c-16, ddc > working: false] complete > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 6064] Invoking callback > function 0x7fee497c57f0 for event DDCA_Display_Status_Event[ 61.292: > DDCA_EVENT_DISPLAY_DISCONNECTED, card0-DP-6, dref: DDCA_Display_Ref[3], > io_path:/dev/i2c-17, > ddc working: false] in this thread [ 6064] > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 6064] Callback function > 0x7fee497c57f0 for event DDCA_Display_Status_Event[ 61.292: > DDCA_EVENT_DISPLAY_DISCONNECTED, card0-DP-6, dref: DDCA_Display_Ref[3], > io_path:/dev/i2c-17, ddc work > ing: false] complete > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] libddcutil > callback thread 0x7fee1001f590 started > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Started 1 event > callback thread(s) > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Udev event > detected > Feb 07 14:22:39 FredArch kwin_wayland[3454]: Atomic modeset test failed! > Permission denied > Feb 07 14:22:39 FredArch kernel: i915 :00:02.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3454, dev=0xe201, auth=1, DRM_IOCTL_MODE_ATOMIC > Feb 07 14:22:39 FredArch kwin_wayland[3454]: Applying output configuration > failed! > Feb 07 14:22:39 FredArch kernel: i915 :00:02.0: [drm:drm_ioctl] > comm="kwin_wayland", pid=3454, ret=-13 > Feb 07 14:22:39 FredArch kwin_wayland[3454]: Atomic modeset test failed! > Permission denied > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Device /dev/i2c-0 > lacks R/W permissions > Feb 07 14:22:39 FredArch kernel: i915 :00:02.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3454, dev=0xe201, auth=1, DRM_IOCTL_MODE_ATOMIC > Feb 07 14:22:39 FredArch kwin_wayland[3454]: Applying output configuration > failed! > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Device /dev/i2c-1 > lacks R/W permissions > Feb 07 14:22:39 FredArch kernel: i915 :00:02.0: [drm:drm_ioctl] > comm="kwin_wayland", pid=3454, ret=-13 > Feb 07 14:22:39 FredArch org_kde_powerdevil[3781]: [ 4027] Device /dev/i2c-2 > l
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #6 from Zamundaaa --- Okay, so one suspicious thing is this: > [ 115.096076] i915 :00:02.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe201, auth=1, DRM_IOCTL_DROP_MASTER > [ 115.096115] nvidia :01:00.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe200, auth=1, DRM_IOCTL_DROP_MASTER right before KWin would normally turn off the screens before suspend. After wakeup, it does > [ 145.491052] i915 :00:02.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe201, auth=1, DRM_IOCTL_SET_MASTER > [ 145.491068] nvidia :01:00.0: [drm:drm_ioctl] comm="systemd-logind" > pid=2439, dev=0xe200, auth=1, DRM_IOCTL_SET_MASTER but only after KWin attempts to turn the display on again. I don't quite understand why systemd would do that, and it certainly doesn't do that on my PC. My first suspicion would be that lact is doing something weird, another possibility is that you have a service or something that causes this. The screens turning on when you press something on the keyboard is most likely because that just triggers a repaint, and makes KWin try again to turn the display(s) on. Can you try removing lact and check if it still happens then? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #5 from Frederick Zhang --- Created attachment 189286 --> https://bugs.kde.org/attachment.cgi?id=189286&action=edit DRM debug log. Captured when using external displays The context around the 'Permission denied' logs in journalctl was > Feb 07 01:24:09 FredArch rtkit-daemon[3544]: Resumed scheduling 6 threads. > Feb 07 01:24:09 FredArch kernel: i915 :00:02.0: [drm:drm_file_free] > comm="lact", pid=2669, dev=0xe280, open_count=23 > Feb 07 01:24:09 FredArch lact[2669]: 2026-02-06T14:24:09.871308Z INFO > lact_daemon::suspend: suspend/resume event detected, reloading config > Feb 07 01:24:09 FredArch kwin_wayland[3470]: Atomic modeset test failed! > Permission denied > Feb 07 01:24:09 FredArch kwin_wayland[3470]: Setting dpms mode failed! > Feb 07 01:24:09 FredArch kwin_wayland[3470]: Atomic modeset test failed! > Permission denied > Feb 07 01:24:09 FredArch kwin_wayland[3470]: Setting dpms mode failed! > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3470, dev=0xe200, auth=1, > DRM_IOCTL_MODE_CREATEPROPBLOB > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3470, dev=0xe200, auth=1, DRM_IOCTL_MODE_ATOMIC > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland", pid=3470, ret=-13 > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3470, dev=0xe200, auth=1, > DRM_IOCTL_MODE_DESTROYPROPBLOB > Feb 07 01:24:09 FredArch kernel: [drm:drm_mode_object_put.part.0] OBJ ID: 165 > (2) > Feb 07 01:24:09 FredArch kernel: [drm:drm_mode_object_put.part.0] OBJ ID: 165 > (1) > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3470, dev=0xe200, auth=1, > DRM_IOCTL_MODE_CREATEPROPBLOB > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3470, dev=0xe200, auth=1, DRM_IOCTL_MODE_ATOMIC > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland", pid=3470, ret=-13 > Feb 07 01:24:09 FredArch kernel: nvidia :01:00.0: [drm:drm_ioctl] > comm="kwin_wayland" pid=3470, dev=0xe200, auth=1, > DRM_IOCTL_MODE_DESTROYPROPBLOB > Feb 07 01:24:09 FredArch kernel: [drm:drm_mode_object_put.part.0] OBJ ID: 165 > (2) > Feb 07 01:24:09 FredArch kernel: [drm:drm_mode_object_put.part.0] OBJ ID: 165 > (1) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 Zamundaaa changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||[email protected] --- Comment #4 from Zamundaaa --- Okay, so there seem to be two things happening here. I see > Feb 06 00:23:20 FredArch kwin_wayland[2633]: Atomic modeset test failed! > Permission denied > Feb 06 00:23:20 FredArch kwin_wayland[2633]: Setting dpms mode failed! which certainly explains why the screens don't turn on, but also > Detected GPU reset on secondary GPU /dev/dri/card0 which is also potentially a problem. Let's ignore the GPU reset for now and find out why KWin doesn't have permissions to turn the screen back on. Please follow https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues and get a drm debug log from a sleep+wake cycle. It will hopefully have more information about what's going on. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #3 from Frederick Zhang --- > I opened my laptop's lid to reach the internal keyboard in Step 3, so that > the 'Lid opened / closed' logs could serve as dividers. *in Step 4* -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #2 from Frederick Zhang --- Created attachment 189242 --> https://bugs.kde.org/attachment.cgi?id=189242&action=edit Logs when using the external displays -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 515550] Screens don't light up automatically after waking up (resuming) from suspend to RAM (sleep) when using Wayland
https://bugs.kde.org/show_bug.cgi?id=515550 --- Comment #1 from Frederick Zhang --- Created attachment 189241 --> https://bugs.kde.org/attachment.cgi?id=189241&action=edit Logs when using the internal screen -- You are receiving this mail because: You are watching all bug changes.
