Kde version: 4.12.3 (was not in the list) I removed .kde4 directory because I had plasma broken after upgrade. So when I rebooted clean starting dolphin took almost a minute. Then it froze after a "control" click. I opened gwenview, it frozed on F11 press. Then I opened the KDE System Settings, which froze. The message in the console was similar to [code] dolphin(25687)/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." [/code] Then I found this half-year old thread. https://bbs.archlinux.org/viewtopic.php?pid=1389739#p1389739 The last message suggested disabling upower, what indeed helped for me After disabling upower and reboot, everything was responsive. Reproducible: Always Steps to Reproduce: 1. Open any Kde application (surely reproduce on dolphin, gwernview and System Settings, but looks like it should freeze any application) 2. Press some buttons. Actual Results: Application freezed Expected Results: Application responsive. ArchLinux x64, 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux btrfs filesystem
After upgrading KDE 4.12.2 to 4.12.3, many issues arose, all of which was ameliorated by masking the upower service. I'm do not possess the proper KDE vocabulary concisely detail the symptoms. This will be a very unsophisticated bug report. But I thought I should add my "Me too!" since I had far different symptoms than the original bug reporter. My xorg.log and xsession-errors files show nothing remarkable. The only pertinent error appears in kdm.log. ------- K D M . L O G ---------------------------------------------------------------------------------------------------- klauncher(3666) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(3660)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" Kdmgreet(3660)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned -------------------------------------------------------------------------------------------------------------------------------- --- T O R E P R O D U C E ------------------------------------------------------------------------------------------- Step 1: Login. (Tested with KDM and XDM) Observe that KDE Splash icons, which normally appear within 3-5 seconds, are taking approximately a minute. While still at the splash screen, KDE issues an "alarm sound" and displays a message about not being able to regulate power because there is no "appropriate handler" (sorry, i don't remember the exact words; the error message disappears kind of quickly). Eventually the desktop appears, only to disappear again, after which a message is displayed which reads that plasma has crashed. It seems as though plasma restarts, and then the desktop is back. However, the entire desktop is unresponsive. Attempting to launch Dolphin gives a launched feedlack (icon bouncing near the cursor), but then it disappears and Dolphin has not launched. Same with all of the applications. ----------- V I T A L S ------------------------------------------------------------------------------------------------- $ uname -a Linux tera 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux $ pacman -Qi kdebase-runtime | grep Version Version : 4.12.3-1 -------------------------------------------------------------------------------------------------------------------------------- Expected Results: Is a rainbow made of chocolate too must to ask?
Please disregard my previous comments. The issue was with upower not finding the libplist.so.1 library. This was caused by installing libplist-git, which upgraded libplist.so.6 to libplist2.so.6. Removing libplist-git and reinstalling libplist has everyone back to normal.
Well, I dont have libplist-git nor libplist installed. And libplist is not a upower dependency.
@docd I can't be sure what the issue is for you. For myself, the issue was /usr/lib/upower/upowerd: error while loading shared libraries: libplist.so.1: cannot open shared object file: No such file or directory listplist is not a dependency of upower. However: $ whoneeds libplist Packages that depend on [libplist] amarok ifuse k3b kaudiocreator kdebase-dolphin kdebase-kdepasswd kdebase-kdialog kdebase-keditbookmarks kdebase-kfind kdebase-konq-plugins kdebase-konqueror kdebase-konsole kdebase-kwrite kdebase-plasma kdebindings-python2 kdeedu-kalzium kdegraphics-gwenview kdegraphics-ksnapshot kdegraphics-okular kdegraphics-thumbnailers kde-gtk-config kde-meta-kdepim kdemultimedia-kmix kdepim-kontact kdeplasma-addons-applets-icontasks kdeplasma-addons-applets-luna kdeplasma-applets-homerun kdeplasma-applets-redshift kdesdk-kate kdeutils-kcalc kdeutils-kwalletmanager kdeutils-print-manager kpartsplugin ktorrent kwebkitpart libgpod libimobiledevice libreoffice-kde4 yakuake Try running upower directly, or checking your logs, to find the reason.
I confirm this bug. It freezes Dolphin in details view (I think because it shows the date).
The bug is present in Kubuntu 14.04 with KDE 4.13.
Created attachment 86509 [details] full gdb backtrace.
If the ktimezone calls freeze waiting for a reply, it usually means that kded4 is not running, or is waiting for something else. If it is indeed running, could you please check which kded module causes the wait? For more information, please see No response, changing status. If you have more information, please add a comment.
C&P error. I meant: For more information, please see http://kdepepo.wordpress.com/2011/05/11/troubleshooting-kded4-bugs/
I have same problem with Dolphin and many apps.
I have the same problem with D-Bus and the time zones: dolphin(18586)/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 run Kubuntu 15.04 but I have Awesome WM as my window manager, there is no KDE session.
I see the exact same issue in Mageia 5 (reported there: https://bugs.mageia.org/show_bug.cgi?id=16583).
I think the same happens with Kate, Kile. As per the suggestion in <https://bbs.archlinux.org/viewtopic.php?pid=1174495#p1174495>, kile runs much faster when executing `dbus-launch --exit-with-session kile`.
Versioning details: Qt: 4.8.7 KDE Development Platform: 4.14.10 kde4-config: 1.0
Seconded. Akregator is unresponsive: 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." Fedora 24 alpha qt5-qtbase-5.6.0-0.38.rc.fc24.x86_64 qt-4.8.7-9.fc24.x86_64 akregator-15.12.2-1.fc24.x86_64 kf5-15.12.2-1.fc24.x86_64 kdelibs-4.14.17-5.fc24.x86_64
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!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
As mentioned in this downstream report in Mageia: https://bugs.mageia.org/show_bug.cgi?id=16583 the issue seems fixed in current versions.