Hi all,
i just upgraded to kubuntu 12.04 (kde4.8.3) and it seems i have a serious bug.
Every time i start dolphin, it takes about 60 seconds until the app window shows up.
If the window finally shows, i get the following message:

dolphin(3520)/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."

I also cleaned out my whole home dir including .kde and .kderc, but the problem still occurred.
This happens on a fresh install of Kubuntu12.04 64 bit.

Can anybody assist in finding the cause of this problem, it's really annoying.
Many thanks in advance!
Greetings, -chris-

Could you try to also remove or rename ~/.pulse and check if that helps?

freininghaus wrote:Could you try to also remove or rename ~/.pulse and check if that helps?

That didn't help. I cleaned out all my home dir, but nothing changed.
Yesterday I updated to KDE4.8.4 and the problem was gone. So it seems that bug has been fixed. And i also think this bug did not affect dolphin alone. I had similar freezes with plasmoids, rekonq and systemsettings. So maybe i posted in the wrong category.

Props to the KDE team!

Greetings, -chris-

This bug would have been caused by issues with DBus. KDE Daemon (kded4) hosts a module called ktimezoned. Because Dolphin could not get a response from it, it had hung until it timed out. All KDE applications use DBus to different extents, which explains why System Settings and Plasma Desktop were also affected.

Good to hear this was solved by a update.

I'm having the exact same problem with al my KDE apps after an update to Kubuntu 13.04.

Pretty unusable. Any ideas how I can debug this further?

jtietema: Are you seeing any KDE Daemon (kded4) crashes, and if not can you confirm that it is running?

I can confirm kded4 is running. Are crashes logged somewhere? Then I can check.

Some other observations:
* the problem is gone when using a fresh user account (so it should be a config problem)
* I moved my .kde folder, but that had no effect, the problem is still there
* other kde apps also freeze for 60 seconds at certain actions or take that time to startup
* kde workspace starts with compositing turned of (posibly because it thinks the slowness is from the GPU not keeping up, which is not the case)

To my knowledge, they're not logged anywhere specifically - however indications of crashes occurring may be logged in ~/.xsession-errors.
If you haven't disabled all debug areas in kdebugdialog, then there may be quite a bit of information in this file though.

The messages are not timestamped, so it is hard to tell which error occurred when.

Anyway I fixed the problem as follows:
moved my .config directory
after logging back in to kde move all folders not present in the newly created .config directory from my old one over to the new one.

KDE now works perfectly and I didn't lose important settings, so this is good enough for me.

Thanks for the help bcooksley.

Hi all,

I had the same problem after actualization of dbus package in debian stable. Reading jtietema, I wondered if akonadi could be the problem, so I remove ~/.config/akonadi and switched off/on the KDE session.
The problem is gone and ~/.config/akonadi is normally recreated.

I hope could be a light on the bug, possibly a version item.

greetings
Frosa