Bug 484500

Summary:	No suspend after kde-inhibit until activity
Product:	[Plasma] plasmashell	Reporter:	Tom <kdebugs>
Component:	Power management & brightness	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	cwo.kde, natalie_clarius, nate
Priority:	NOR
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	NixOS
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Tom 2024-03-26 03:45:55 UTC

SUMMARY

`kde-inhibit --power` correctly stops automatic power management (sleep) while it's running, but after it completes, automatic power management is still inhibited until the user interacts with the computer.

STEPS TO REPRODUCE

1. In System Settings -> Energy Saving, set the Suspend Session timer to 1 minute.
2. Run `kde-inhibit --power sleep 90`
3. See that power management was successfully inhibited, since the computer didn't suspend.
4. Don't touch anything.
5. See that the computer does NOT sleep after 60 seconds, even though kde-inhibit exited.
6. Move the mouse or use the keyboard.
7. Wait 60 seconds and see the computer suspend automatically.

OBSERVED RESULT

Computer did not automatically sleep after set period after kde-inhibit exited.

EXPECTED RESULT

Computer should automatically sleep after the set period, starting after kde-inhibit exits.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: NixOS 24.05 (unstable), Linux kernel 6.8.1, Wayland
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

Comment 1 cwo 2024-09-20 18:17:37 UTC

Can reproduce on git master (Tuxedo OS).

But I don't think this is a kde-inhibit issue; the same thing happens with systemd-inhibit. Could be a kde issue or somewhere lower in the stack. Reassigning to powerdevil so our power management experts can have a look.

Comment 2 Natalie Clarius 2024-09-21 20:22:48 UTC

I can't reproduce this on git master, the computer goes to sleep for me after the 90 + 60 seconds without interaction.

Comment 3 Nate Graham 2025-03-07 20:21:32 UTC


*** This bug has been marked as a duplicate of bug 491922 ***