https://bugs.kde.org/show_bug.cgi?id=473392
knd...@outlook.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|5.27.3 |5.27.7
Resolution|BACKTRACE |---
Status|NEEDSINFO |REPORTED
--- Comment #2 from knd...@outlook.com ---
The backtrace was sloppy the first time because I had built the package from
AUR with `!debug` and `strip` enabled by default. I updated it to the latest
powerdevil and built it with debug symbols this time. systemd-coredumpd does
not seem to catch the backtrace again, but I'll give it another shot.
I simplified the crash to a much simpler case. powerdevil crashes and aborts on
logging out. Here's the rough timeline. Logs attached at the end.
1. Cold boot
2. Log in: SDDM is still on X11 because wayland does not work for me
3. Log out: no errors related to powerdevil until this point
org_kde_powerdevil[1136]: The Wayland connection broke. Did the Wayland
compositor die?
systemd[890]: Starting Powerdevil...
systemd[890]: plasma-powerdevil.service: Scheduled restart job, restart counter
is at 1.
org_kde_powerdevil[1596]: Failed to create wl_display (No such file or
directory)
org_kde_powerdevil[1596]: This application failed to start because no Qt
platform plugin could be initialized. Reinstalling the application may fix this
problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl,
wayland-xcomposite-glx, xcb.
org_kde_powerdevil[1596]: qt.qpa.plugin: Could not load the Qt platform plugin
"wayland" in "" even though it was found.
systemd[890]: Failed to start Powerdevil.
systemd[890]: plasma-powerdevil.service: Failed with result 'core-dump'.
systemd[890]: plasma-powerdevil.service: Main process exited, code=dumped,
status=6/ABRT
Note: A lot of other kde services such as kdeconnectd, krunner,
kactivitymanagerd, plasmashell, kwalletd5, kded5 die with similar error
message. plasmashell produces a core dump when systemd tries to restart it:
`plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.`
To summarize, can we reduce the scope of this bug to finding the reason why
services automatically start after a logout?
--
You are receiving this mail because:
You are watching all bug changes.
