What is waking my wayland screen sleep?

hornetster · January 5, 2026, 3:20am

Can’t get my computer to lock/turn off screen.
Settings should be fine (KDE/Plasma):
Lock Screen = 10mins - shortcut set and works
Turn off screen 10 minutes, and again shortcut works, but…
Never notice it trying to lock, or screen off automatically. When manually turning off screen, it turns back on almost immediately.
None of this appears to be in journalctl, or dmesg? Is it logged somewhere? How can I chase it up?
Thanks,
John.

Tumbleweed updated…
KDE Plasma Wayland(Mostly…)
Lenovo M920S, i5, 16GB.
Dell Ultrasharp, U3415W

deano_ferrari · January 5, 2026, 4:02am

Check for any stray input that might keep triggering the system to stay awake
libinput debug-events
Run this without touching the keyboard or mouse. If events keep appearing, KDE Plasma won’t consider the system idle.

Try forcing the display off with kscreen-doctor --dpms off. Does it stay off, or turn back on immediately? If it turns back on, that points to a hardware/DisplayPort wake issue rather than a KDE Plasma problem.

malcolmlewis · January 5, 2026, 4:09am

Also what GPU? Can you post the output from inxi -GSaz.

karlmistelberger · January 5, 2026, 4:49am

Some problems arose when switching an Intel system to Wayland. The monitor was attached with a HDMI cable:

n150:~ # inxi -CG
CPU:
  Info: quad core model: Intel N150 bits: 64 type: MCP cache: L2: 2 MiB
  Speed (MHz): avg: 700 min/max: 700/3600 cores: 1: 700 2: 700 3: 700 4: 700
Graphics:
  Device-1: Intel Alder Lake-N [Intel Graphics] driver: i915 v: kernel
  Display: unspecified server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.8 driver: X:
    loaded: modesetting unloaded: vesa dri: iris gpu: i915 tty: 236x52 resolution: 3840x2160
  API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.3.1 note: console (EGL sourced)
    renderer: Mesa Intel Graphics (ADL-N), llvmpipe (LLVM 21.1.7 256 bits)
  API: Vulkan v: 1.4.335 drivers: intel,llvmpipe surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
n150:~ #

erika@n150:~> journalctl --user --boot 5c8bf8a42d77437dbcae5fd17d81a227 --unit plasma-powerdevil --priority warning 
Okt 30 17:25:31 n150 org_kde_powerdevil[1331]: [  1331] Watching for DPMS state changes unimplemented
Okt 30 17:25:31 n150 org_kde_powerdevil[1331]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okt 30 17:25:31 n150 org_kde_powerdevil[1331]: org.kde.powerdevil.backlighthelper.brightness failed
Okt 30 17:25:31 n150 org_kde_powerdevil[1331]: Handle button events action could not check for screen configuration
Okt 30 17:25:31 n150 org_kde_powerdevil[1331]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okt 30 17:25:51 n150 org_kde_powerdevil[1331]: [  1543] (dw_remove_display_by_businfo) No Display_Ref found for i2c bus: 1
Okt 30 17:25:58 n150 org_kde_powerdevil[1331]: [  1543] busno=1, sleep-multiplier= 1,00.Retesting for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(6), DDCRC_NULL_RESPONSE>
Okt 30 17:25:58 n150 org_kde_powerdevil[1331]: [  1543] ddc_initial_checks_by_dref() returned DDCRC_RETRIES(-3007): maximum retries exceeded
Okt 30 17:27:47 n150 org_kde_powerdevil[2487]: [  2487] Watching for DPMS state changes unimplemented
Okt 30 17:27:47 n150 org_kde_powerdevil[2487]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okt 30 17:27:47 n150 org_kde_powerdevil[2487]: org.kde.powerdevil.backlighthelper.brightness failed
Okt 30 17:27:47 n150 org_kde_powerdevil[2487]: Handle button events action could not check for screen configuration
Okt 30 17:27:47 n150 org_kde_powerdevil[2487]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okt 30 17:39:44 n150 org_kde_powerdevil[2487]: [  2632] (dw_remove_display_by_businfo) No Display_Ref found for i2c bus: 1
Okt 30 17:39:48 n150 org_kde_powerdevil[2487]: [  2632] busno=1, sleep-multiplier= 1,00.Retesting for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(6), DDCRC_NULL_RESPONSE>
Okt 30 17:39:48 n150 org_kde_powerdevil[2487]: [  2632] ddc_initial_checks_by_dref() returned DDCRC_RETRIES(-3007): maximum retries exceeded
Okt 30 19:23:36 n150 org_kde_powerdevil[2487]: [  3030] (dw_remove_display_by_businfo) No Display_Ref found for i2c bus: 1
Okt 30 19:23:41 n150 org_kde_powerdevil[2487]: [  3030] busno=1, sleep-multiplier= 1,00.Retesting for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(6), DDCRC_NULL_RESPONSE>
Okt 30 19:23:41 n150 org_kde_powerdevil[2487]: [  3030] ddc_initial_checks_by_dref() returned DDCRC_RETRIES(-3007): maximum retries exceeded
Okt 30 19:33:53 n150 org_kde_powerdevil[2487]: [  3449] (dw_remove_display_by_businfo) No Display_Ref found for i2c bus: 1
Okt 30 19:33:59 n150 org_kde_powerdevil[2487]: [  3449] busno=1, sleep-multiplier= 1,00.Retesting for supported feature 0x10 returned Error_Info[DDCRC_RETRIES in ddc_write_read_with_retry, causes: DDCRC_DDC_DATA(6), DDCRC_NULL_RESPONSE>
Okt 30 19:33:59 n150 org_kde_powerdevil[2487]: [  3449] ddc_initial_checks_by_dref() returned DDCRC_RETRIES(-3007): maximum retries exceeded
Okt 30 19:35:29 n150 org_kde_powerdevil[2487]: org.kde.powerdevil.chargethresholdhelper.getconservationmode failed "Battery conservation mode is not supported"
Okt 30 19:35:29 n150 org_kde_powerdevil[2487]: org.kde.powerdevil.chargethresholdhelper.getconservationmode failed "Battery conservation mode is not supported"
Okt 30 19:36:29 n150 org_kde_powerdevil[2487]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okt 30 19:36:50 n150 org_kde_powerdevil[2487]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
erika@n150:~>

Switching to DisplayPort eventually stopped the annoyances:

erika@n150:~> journalctl --user --boot 0 --unit plasma-powerdevil --priority warning 
Jan 03 16:59:28 n150 org_kde_powerdevil[1307]: Connection to Wayland server timed out.
Jan 03 16:59:28 n150 org_kde_powerdevil[1307]: Connection to Wayland server timed out.
Jan 03 16:59:28 n150 org_kde_powerdevil[1307]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Jan 03 16:59:28 n150 org_kde_powerdevil[1307]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.org_kde_powerdevil'")
Jan 03 16:59:28 n150 org_kde_powerdevil[1307]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.org_kde_powerdevil'")
Jan 03 16:59:28 n150 org_kde_powerdevil[1307]: org.kde.powerdevil.backlighthelper.brightness failed
Jan 03 16:59:28 n150 org_kde_powerdevil[1307]: Handle button events action could not check for screen configuration
Jan 03 16:59:29 n150 org_kde_powerdevil[1307]: Connection to Wayland server timed out.
Jan 03 16:59:29 n150 org_kde_powerdevil[1307]: Handle button events action could not check for screen configuration
Jan 03 16:59:29 n150 org_kde_powerdevil[1307]: QObject::connect(QObject, ConfigMonitor::Private): invalid nullptr parameter
Jan 03 16:59:29 n150 org_kde_powerdevil[1307]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
erika@n150:~>

Several warnings are displayed during startup. No further messages have been observed during two days of continuous operation.

hui · January 5, 2026, 5:30am

Also check the energy/battery applet in the Plasma taskbar. It also can tell you which application prevents lock/screen off. There you also have the possibility to override this.

hornetster · January 5, 2026, 9:19am

Thanks for all the replies/suggestions, decided to do a full reset/reseat/clean of components/cables, and it seems to have settled it down - now appears to be working ‘almost’ OK!
Appreciated.

deano_ferrari · January 5, 2026, 9:26am

Thanks for the update. Good to start with the simple stuff first.

system · January 12, 2026, 9:27am

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.