Bug 493901 - (wayland) DPMS / "Turn off Screen [time]" does not work.
Summary: (wayland) DPMS / "Turn off Screen [time]" does not work.
Status: RESOLVED WORKSFORME
Alias: None
Product: Powerdevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 6.1.5
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-01 07:35 UTC by Steve Vialle
Modified: 2024-10-02 05:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Vialle 2024-10-01 07:35:14 UTC 
SUMMARY
Display power save timeout setting has no effect in wayland session, screen never blanks even with delay set to 1 minute inactivity.

STEPS TO REPRODUCE
1. Wayland session
2. Set "Turn off screen" to some value
3. Wait

OBSERVED RESULT
Screen never blanks.

EXPECTED RESULT
Screen blank / DPMS activates after configured inactivity timeout.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.6.51-gentoo-dist (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Screenlocker / "Lock screen automatically" works normally in both wayland and x11.
No pm-inhibiting applications (e.g. video players, etc.) are running, this is a fresh login with only firefox and systemsettings open.
This is a desktop system, so no batteries or other mobile power management shenanigans should be involved.
(belatedly) assuming this is not #493546, since that is an x11 session.
Comment 1 Steve Vialle 2024-10-02 05:50:45 UTC 
Well nevermind then, this has mysteriously fixed itself after some restart/login-logout cycles.

I have no real idea what happened, but I'm guessing some component crashed since I have a bunch of time-relevant QT related drama in syslog.
Idle blanking problems haven't happened again since this report, QT crashes will get their own if they recur.

FWIW:
localhost kernel: QSGRenderThread[7311]: segfault at 8 ip 00007fb1fd886d38 sp 00007fb1bd0be8a0 error 4 in libQt6Core.so.6.7.2[7fb1fd68d000+371000] likely on CPU 0 (core 0, socket 0)

Dunno who 7311 was at the time or why they died though.

Closing.