Bug 433965 - kiod crashlooping
Summary: kiod crashlooping
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.79.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-04 18:20 UTC by Martin Sandsmark
Modified: 2021-04-04 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Sandsmark 2021-03-04 18:20:04 UTC
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...
Comment 1 Nate Graham 2021-03-05 20:04:42 UTC
Can you attach an example crashlog?
Comment 2 Bug Janitor Service 2021-03-20 04:33:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2021-04-04 04:33:44 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!