Bug 506062

Summary:	powerdevil is not starting since Plasma 6.4
Product:	[Plasma] plasmashell	Reporter:	jonathan.lieb
Component:	Power management & brightness	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bshah, chaitanya.chalasani, walmartshopper
Priority:	NOR
Version First Reported In:	6.4.0
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description jonathan.lieb 2025-06-23 16:54:20 UTC

SUMMARY
Hello,
on my Fedora 42 the plasma-powerdevil.service is not starting up. It was working before the update.
In my journalctl i found:

Jun 23 17:27:10 fedora systemd[2634]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1.
Jun 23 17:27:10 fedora systemd[2634]: Starting plasma-powerdevil.service - Powerdevil...
Jun 23 17:27:10 fedora (werdevil)[3260]: plasma-powerdevil.service: Failed to apply ambient capabilities (before UID change): Operation not permitted
Jun 23 17:27:10 fedora (werdevil)[3260]: plasma-powerdevil.service: Failed at step CAPABILITIES spawning /usr/libexec/org_kde_powerdevil: Operation not permitted
Jun 23 17:27:10 fedora systemd[2634]: plasma-powerdevil.service: Main process exited, code=exited, status=218/CAPABILITIES
Jun 23 17:27:10 fedora systemd[2634]: plasma-powerdevil.service: Failed with result 'exit-code'.
Jun 23 17:27:10 fedora systemd[2634]: Failed to start plasma-powerdevil.service - Powerdevil.

I deleted the parameter AmbientCapabilities=CAP_WAKE_ALARM in the service file and now it is working again. The think the parameter is new.

STEPS TO REPRODUCE
1. Update or Install KDE 6.4 on Fedora 42
2. journalctl --user -u plasma-powerdevil.service
3. Delete AmbientCapabilities=CAP_WAKE_ALARM in /usr/lib/systemd/user/plasma-powerdevil.service

OBSERVED RESULT
Powermanagment is not working 

EXPECTED RESULT
Powermanagment is working

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.14.11-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 14 × Intel® Core™ Ultra 5 125U
Memory: 32 GiB of RAM (30.8 GiB usable)
Graphics Processor: Intel® Graphics

ADDITIONAL INFORMATION

Comment 1 walmartshopper 2025-06-23 17:34:39 UTC

Affected me also on Arch after upgrading to 6.4.0.  Same errors in journalctl.  But rather than deleting the AmbientCapabilities line from the service file, I did:

systemctl --user edit plasma-powerdevil

and then entered the following override:

[Service]
AmbientCapabilities=

Comment 2 Antonio Rojas 2025-06-23 18:56:49 UTC


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

Comment 3 Bhushan Shah 2025-06-25 10:34:03 UTC

Hi Jonathan, Please see duplicated comment in last thread, do you have such an special setup?

Comment 4 Chaitanya Chalasani 2025-06-25 12:53:14 UTC

I do have the same issue on the similar setup.

Comment 5 walmartshopper 2025-06-25 16:51:23 UTC

Can confirm that my uid was the issue.  My uid has always been 501 since Slackware ~20 years ago.  Changing my uid to 1000 solved this issue plus a long-standing issue I had with KDE's user management not working.  SDDM will also work now without having to change the minimum uid.

Comment 6 jonathan.lieb 2025-06-27 15:39:53 UTC

(In reply to Bhushan Shah from comment #3)
> Hi Jonathan, Please see duplicated comment in last thread, do you have such
> an special setup?
Hi,
can i can confirm that i works with "normal" uids (1000) on my private Fedora. The Issue is on my work laptop with sssd and an Mircosoft AD integration. UIDs are way higher. When you need the exact uid we have to wait until monday.