https://bugs.kde.org/show_bug.cgi?id=523101
Bug ID: 523101
Summary: Should powerdevil always restart
Classification: Plasma
Product: plasmashell
Version First 6.5.5
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Power management & brightness
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
***
If you're not sure this is actually a bug or valid feature request, instead
post about it at https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Please remove this comment after reading and before submitting - thanks!
***
DESCRIPTION
It's possible for a crash in the system to kill powerdevil without the service
reporting a "failure". Since the systemd service is set to restart only on
failure, the service does not restart. This leads to a situation where the
battery indicator is unavailable.
I'm not sure about how to reproduce a crash where the service is killed instead
of failing. However, I had it happen once on my system
STEPS TO REPRODUCE
1. Wait for a crash that kills the service. Or manually kill the service (I
didn't test this)
OBSERVED RESULT
systemctl --user status plasma-powerdevil
○ 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: inactive (dead) since Wed 2026-07-15 22:31:38 +07; 53min ago
Duration: 6d 6h 55min 25.291s
Invocation: a293a680ad21449590e8ae78501b7adb
Process: 2989 ExecStart=/usr/libexec/org_kde_powerdevil (code=killed,
signal=TERM)
Main PID: 2989 (code=killed, signal=TERM)
Mem peak: 14M (swap: 5.1M)
CPU: 1min 39.133s
jul 15 22:31:33 student-laptop org_kde_powerdevil[2989]: Failed to play sound
with canberra: File or data not found
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: The Wayland connection
broke. Did the Wayland compositor die?
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: Attempting wayland
reconnect
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: Failed to write to the
pipe: Bad file descriptor.
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: There are no outputs -
creating placeholder screen
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: X connection to :0
broken (explicit kill or server shutdown).
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: QtDBus: cannot relay
signals from parent QObject(0x561d2d688b70 "") unless they are emitted in the
object's thread QThread(0x561d2>
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: QSocketNotifier:
Socket notifiers cannot be enabled or disabled from another thread
jul 15 22:31:38 student-laptop org_kde_powerdevil[2989]: [335969] Watch thread
terminated.
jul 15 22:31:38 student-laptop systemd[2179]: plasma-powerdevil.service:
Consumed 1min 39.133s CPU time, 14M memory peak, 5.1M memory swap peak.
EXPECTED RESULT
The service always restarts. It seems like a service that is critical enough to
always restart. I'm not sure how other kde services are configured, but it may
be relevant for others as well.
If there are good reasons for not setting the service to Restart=Always I'm
also interested to know.
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.10.3
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
