The KDialog file chooser (--getsavefilename option) sometimes takes a long time before the window pops up; when this is happening, it also takes a long time for the choice to get back to the caller. When this starts happening, it continues happening every time the file chooser is used, until KDE is restarted. Reproducible: Sometimes When run from the command line while the bug is happening, the following lines are sent to stdout/stderr shortly before the window pops up: > kdialog(7721)/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." > Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) > Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) strace shows the pause happening in poll(), and ltrace shows it happening in KFileItem::KFileItem(unsigned int, unsigned int, KUrl const&, bool)
Do you have remote folders in the places panel?
There's a "Network" entry which has a location of "remote:/", and lists "Network", "Network Services" and "Samba Shares" (all of them shown in italics). However, it's normally hidden. I have Dropbox installed, and am also using the computer as an NFS server for a VMWare player which runs on the same computer, but running those things doesn't start the problem.
So it looks something blocks the session D-Bus. This could either be caused by a kded module, or even a third-party application or component. Can you reproduce the steps to make it block? If seems to appear automatically only after using the machine for some time, it could be related to packages update modules. To check if a kded module is responsible, please follow http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/
Some further information from when it happened again: * There were three defunct kded processes. * Trying to open up any of the folders under the "Network" group would cause a long delay, when there's no delay when the bug isn't present. * Stopping and then starting the D-Bus service didn't help.
You could try disabling the faulty kded module. For instructions, see the link from comment #3.
Okay, I've disabled the network related services and the time-zone service. If the problem recurs even with these turned off, I'll report immediately. If the bug doesn't recur for a while, I'll note that.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
I haven't seen this problem in a while.
Thanks for the update!