kde session hangs when konqueror/rekonq interacts with kcookiejar

[avlas]

While Konqueror/Rekonq (and then actually the whole KDE system) hangs (and stays like that from seconds to minutes) I get this sort of messages:

konqueror(21899)/kio (AccessManager) KIO::Integration::CookieJar::cookiesForUrl: Unable to communicate with the cookiejar!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: kdelibs5-plugins 4:4.12.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Feb 23 11:09:45 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-07-27 (942 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcEnviron:
 LANGUAGE=ca:ca@valencia:en_US:en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ca_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: kde4libs
UpgradeStatus: Upgraded to trusty on 2014-02-17 (6 days ago)

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

[avlas (avlas)]

done:

https://bugs.kde.org/show_bug.cgi?id=331439

[avlas (avlas)]

For the case it may be useful for others, the bug is in the kded daemon for application menus. Since I disabled it, I found no more of these problems in (1) konqueror/rekonq; neither a temporary lapse in which (2) kile was irresponsive on startup (which I realized after filling this bug), as well as in (3) kde telepathy when I tried to open a chat (again with same sort of dbus hangs).

I found the root of the problem because the bug was 100% reproducible in kile not bein responsive on startup until the following message appeared in the terminal:

kile(29554)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

[avlas (avlas)]

More info about the issue and workaround:

I found out that the issue only happens if I put the application menu in either the title bar button or in a menubar at the top of the screen, but not if the menubar appear in the application or I just export it (to use it in another plasma applet).

This issue is only due to this configuration and irrespective of me using another plasma applet to show applications' menubar.

I workaround the problem by just exporting the menu, as I use this plasma-widget-menubar anyways:

http://bazaar.launchpad.net/~kol-93/plasma-widget-menubar/plasma-widget-menubar