https://bugs.kde.org/show_bug.cgi?id=506052

            Bug ID: 506052
           Summary: powerdevil cannot start because of CAP_WAKE_ALARM
    Classification: Plasma
           Product: plasmashell
      Version First 6.4.0
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Power management & brightness
          Assignee: plasma-b...@kde.org
          Reporter: yam...@yamagi.org
  Target Milestone: 1.0

Since Plasma 6.4.0 the powerdevil systemd unit sets
'AmbientCapabilities=CAP_WAKE_ALARM'. powerdevil is spawned as a user service
and can only gain capabilities which the 'systemd --user' service for the
session has:

% ps auxww | grep "systemd --user"
yamagi    1180  0.0  0.0  21804 11744 ?        Ss   07:26   0:01
/usr/lib/systemd/systemd --user 

% cat /proc/1180/status | grep CapAmb
CapAmb: 0000000000000000

-> The 'systemd --user' has no ambient capabilities, therefor it cannot set
'CAP_WAKE_ALARM' and starting powerdevil fails:

% journalctl --user -xu plasma-powerdevil.service
Jun 23 08:52:04 blubb (werdevil)[17116]: plasma-powerdevil.service: Failed to
apply ambient capabilities (before UID change): Operation not permitted
Jun 23 08:52:04 blubb (werdevil)[17116]: plasma-powerdevil.service: Failed at
step CAPABILITIES spawning /usr/lib/org_kde_powerdevil: Operation not permitted

This can be worked around by commenting the
'AmbientCapabilities=CAP_WAKE_ALARM'. Functionality requiring the
CAP_WAKE_ALARM won't work, though.

Linux/KDE Plasma: Arch Linux as of 23.06.2025 ca. 05:00 UTC with Linux
6.15.3-arch1-1 and systemd 257.6-1
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to