https://bugs.kde.org/show_bug.cgi?id=433965
Bug ID: 433965
Summary: kiod crashlooping
Product: frameworks-kio
Version: 5.79.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kio-bugs-n...@kde.org
Reporter: martin.sandsm...@kde.org
CC: kdelibs-b...@kde.org
Target Milestone: ---
Running multiple user sessions on the same X session, and it seems like kiod
isn't using kdeinit anymore.
So whenever something wants to use e. g. kpasswdserver it tries to start kiod
with dbus activation and starts crashlooping.
dbus-daemon[111214]: [session uid=1001 pid=111212] Activating service
name='org.kde.kpasswdserver' requested by ':1.136' (uid=1001 pid=336356
comm="sftp.so [kdeinit5] sftp local:/tmp/runtime-testuser/foo")
kiod5[337539]: qt.qpa.xcb: could not connect to display thulcandra:10.0
kiod5[337539]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in ""
even though it was found.
kiod5[337539]: This application failed to start because no Qt platform plugin
could be initialized. Reinstalling the application may fix this problem. [...]
systemd[1]: Started Process Core Dump (PID 337540/UID 0).
systemd-coredump[337543]: [🡕] Process 337539 (kiod5) of user 1001 dumped core.
Is there a way to force stuff back to using kdeinit? My disk is filling up with
coredumps and the journal is getting unusable...
--
You are receiving this mail because:
You are watching all bug changes.
