https://bugs.kde.org/show_bug.cgi?id=499896
--- Comment #2 from Pavel Dobiáš <pavel23...@proton.me> ---
(In reply to Nicolas Fella from comment #1)
> The systemsettings crash you attached doesn't look related to tuned at all.
>
> Can you please show the output of "systemctl --user status
> plasma-powerdevil.service"?
Here's the output:
```
× plasma-powerdevil.service - Powerdevil
Loaded: loaded (/usr/lib/systemd/user/plasma-powerdevil.service; static)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Wed 2025-02-12 18:05:25 CET;
57min ago
Duration: 27ms
Invocation: 616da5c09beb405baaf574dca4f681da
Process: 6646 ExecStart=/usr/libexec/org_kde_powerdevil (code=exited,
status=255/EXCEPTION)
Main PID: 6646 (code=exited, status=255/EXCEPTION)
Feb 12 18:05:25 fedora systemd[2669]: plasma-powerdevil.service: Scheduled
restart job, restart counter is at 25.
Feb 12 18:05:25 fedora systemd[2669]: plasma-powerdevil.service: Start request
repeated too quickly.
Feb 12 18:05:25 fedora systemd[2669]: plasma-powerdevil.service: Failed with
result 'exit-code'.
Feb 12 18:05:25 fedora systemd[2669]: Failed to start plasma-powerdevil.service
- Powerdevil.
```
Just to clarify idk how much this is a tuned issue or anything, I've only
specified it so it's clear what the stack is.
--
You are receiving this mail because:
You are watching all bug changes.
