After filling a bug in the Ubuntu system (https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/1283753), I was requested to fill it upstream in KDE. 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! Reproducible: Always
If this is reproducible, please check which kded module causes kded to hang. For more information, please see http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/
Thanks for pointing me into this direction. Two conclusions so far: 1- If I completely disable kded4, I get these messages in the terminal but konqueror and the system is responsive 2- If I just move the daemon kcookiejar.desktop out of /usr/share/kde4/services/kded/ I get the messages and again konqueror and the system hangs Both points together seem to indicate to me that kcookiejar.desktop is not actually responsible for the issue (at least by itself). I'll try disabling 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."
Thanks for the update. Reassigning.
More info: 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). I'm going to check now whether this happens because my plasma applet interferes or it is just an issue in appmenu per se.
Confirmed, 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
I can confirm this bug, and that it started happening to me right after updating to Kubuntu 14.04 (KDE 4.13). It happens only when the application menus are set to the title bar, and it's specially painful when using Konqueror. In my case it doesn't hang all the plasma desktop but just Konqueror and some things in Kontact. There's just something terribly wrong when menus are in the title bar that renders applications unusable, so I'd consider this as a critical bug. IN MY OPINION, this bug only happens when a popup window is going to appear (or after appearing) but I can't confirm this 100%. I was just about to ditch Kubuntu and go the Unity way because the system (specifically Konqueror) was just unusable due to the constant freezes, but I decided to do a last research effort hoping there was a fix or something could be done. Luckily I found this bug, but I don't think a lot of people will do the research instead of just ditching KDE like I was planning and I don't think they will change their menu settings out of intuition or something.
I can confirm this bug. When I start Kile I get the same error message like in Comment 3, and using the settings in Comment 5 Kile starts normally. I use Kubuntu 14.04. with KDE 4.13.
This is for the old Plasma 4 implementation. Plasma 5.9 has a new implementation of the menu bar.