Hi, I am not sure if this is the right place, but since the only way for me to get some error messages, when this error occurs, is to launch Dolphin from the terminal and notice the messages. Please help me to submit this bug to the right place. The following error messages appear when the error occurs and then launching dolphin from terminal. Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) "/org/freedesktop/UDisks2/drives/HDD-NAME" : property "Drive" does not exist QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: no permission QFileSystemWatcher: failed to add paths: /var/lib/samba/usershares Terminal shows about 20 sec the error messages until dolphin launches. But when clicking on a folder after Dolphin launched, it takes again a few seconds until folder opens. The whole system seems to get "laggy". The only warning I found in the logs is from auth.log: polkitd(authority=local) Operator of unix-session:/org/freedesktop/ConsoleKit/Session1 FAILED to authenticate to gain authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.36 [/usr/bin/dolphin --icon system-file-manager -caption Dolphin] (owned by unix-user:USERNAME) I am not sure what causes this issue, but most of the time a simply reboot fixes the problem, until it happens again randomly, directly after a new login. Reproducible: Sometimes Dekstop PC Intel Z77 + Intel i5-2400 (Sandy Bridge) Integrated Intel graphics in use Linux 3.12-1-amd64 PLEXTOR SSD formatted as ext4 8GB DDR3 1333
Thanks for the bug report. It's most likely not a problem in Dolphin itself. To investigate which part of the code hangs, please follow the instructions in http://community.kde.org/Dolphin/FAQ/Freeze
Thanks for the hint, it seems like the Dolphin error messages also appear when the system is not hanging, so they are not usefull at all :( Have to find another way to debug this error and also to check the error from auth.log further.
Is this still an issue with newer versions of KDE Plasma/Dolphin? If not, I'll close this bug soon.
No response -> closing. Thanks for reporting this bug, please reopen the report if you can still reproduce this behavior with newer versions of Dolphin.