Bug 429764

Summary: Constant spam of "kf.kio.slaves.http: Can't communicate with kded_kcookiejar!"
Product: [Frameworks and Libraries] frameworks-kio Reporter: Nate Graham <nate>
Component: generalAssignee: KIO Bugs <kio-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: kdelibs-bugs-null, ralf.habacker
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=439934
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nate Graham 2020-11-28 16:00:13 UTC 
For a could of weeks now, I'm getting a near-constant spam of the following output when I run KDE software in a terminal window:

kf.kio.slaves.http: Can't communicate with kded_kcookiejar!
kf.kio.slaves.http: Can't communicate with kded_kcookiejar!
kf.kio.slaves.http: Can't communicate with kded_kcookiejar!
kf.kio.slaves.http: Can't communicate with kded_kcookiejar!
kf.kio.slaves.http: Can't communicate with kded_kcookiejar!



Seems to happen in src/ioslaves/http/http.cpp:4567

I have no idea what this means or if it's significant or how to fix it though.
Comment 1 Nate Graham 2021-03-24 14:50:38 UTC 
Journalctl is filled with this:

Mar 24 08:02:15 Liberator dbus-daemon[1559]: [session uid=1000 pid=1559] Failed to activate service 'org.kde.kcookiejar5': timed out (service_start_timeout=120000ms)
Mar 24 08:02:15 Liberator dbus-daemon[1559]: [session uid=1000 pid=1559] Activating service name='org.kde.kcookiejar5' requested by ':1.1125' (uid=1000 pid=29194 comm="http.so [kdeinit5] https local:/run/user/1000/klau")
Comment 2 Ralf Habacker 2021-07-16 08:06:14 UTC 
kcookiejar5 is a kded service that manages cookies in KDE programs. The source code is located at https://invent.kde.org/frameworks/kio/-/tree/master/src/ioslaves/http/kcookiejar, the binary for example at the opensuse distribution in package kio, is designed as kded module and available as dbus service org.kde.kcookiejar5.
Comment 3 Nate Graham 2022-10-01 16:58:32 UTC 
Not a code issue; this is caused by the Plasma dev setup process which masks the system service, which apparently makes everyone unhappy. It will be fixed once we roll out the next-gen dev session infrastructure with https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1715