Created attachment 692993 [details] dmesg debug output Description of problem: KDE on F18 is freezing often for seconds and nothing can be clicked or done. Version-Release number of selected component (if applicable): Latest version(s). All updates are installed. How reproducible: Mostly. Steps to Reproduce: 1. Start F18 2. Log into KDE 3. Try to open a programm (like kaffeine) 4. System freezes for seconds 5. Programm opens. 6. Try to open a menu from the menu bar 7. Desktop freezes 8. .... Actual results: System is always freezing for seconds, then it continues and freezes again on other actions. Expected results: Nothing should freeze. Additional info: Many DBUS messages in dmesg output. You can see that there is always a break for many seconds, too. This is always when the system is freezing.
it sounds like an old bug in solid-udisk2 which we fixed in the f18 official release. which kdelibs version is installed on your machine? please attach the output of rpm -qi kdelibs thanks
What could be helpful to would be ~/.xsession-errors content when this occurs.
$ rpm -qi kdelibs Name : kdelibs Epoch : 6 Version : 4.9.5 Release : 2.fc18 Architecture: i686 Install Date: Di 22 Jan 2013 18:54:32 CET Group : Unspecified Size : 40694738 License : LGPLv2+ Signature : RSA/SHA256, Do 03 Jan 2013 20:03:39 CET, Key ID ff01125cde7f38bd Source RPM : kdelibs-4.9.5-2.fc18.src.rpm Build Date : Mi 02 Jan 2013 13:46:23 CET Build Host : buildvm-20.phx2.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : http://www.kde.org/ Summary : KDE Libraries Description : Libraries for KDE 4. I don't know if this matters: I installed F18, before it got final for testing. Could it be possible that there was something left, that wasn't update though the updates I daily install via yum?
Created attachment 693888 [details] .xession-errors I installed all the latest available updates and rebootet, to make sure everything is up-to-date an restarted. - I logg into KDE - I start Kaffeine - Nothing appears for about 20 seconds and nothing is clickable any more (like in the Startbar) - Then the empty Kaffeine window appears - KDE freezes for about another 20-30 seconds. Then the windows content is shown. - I click to the menu TV / Configure (I'm not sure, if this is the english wording. On my german system it's "Fernsehen" / "Konfigurieren") - KDE freezes again and nothing is clickable for about 1 minute - The TV configure window appears - I close the application - I open the console and have a first look into .xsession-errors. - I open firefox (starts without problem) - Logg into Bugzilla and start writing the bugreport until this line - I start Kaffeine again now (system is up now for about 8 minutes) - Same. KDE freezes and nothing is clickable. But I can switch between Konsole an the Firefox window with [Alt]+[Tab] - After about 20 seconds, the Kaffeine window appears, but empty again - Another 20-30 seconds later, the window is shown - I close Kaffeine again - Now I attach the .xsession-errors file.
I just wanted to give one more information: When this happens and I click to start / shutdown, KDE also freezes. After it's unfrozen again, I have to click start / shutdown again, then the window appears, where I have to choose log-off/restart/shutdown. I click shutdown and the system goes down.
kaffeine(997)/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." 20 seconds hang corresponds to DBus call timeout, which means that ktimezoned KDED daemon is not loaded when calling it's intialize() method. Make sure kde-runtime is installed properly and check whether you can load ktimezoned manually. Invoking qdbus org.kde.kded /kded org.kde.kded.loadModule ktimezoned should print "true"
Can you please test: https://admin.fedoraproject.org/updates/FEDORA-2013-1932 ? It fixes a ktimezoned issue, and might actually fix this bug as an unintentional but welcome side effect. You can use the following to test a specific update or update group from updates-testing: yum install yum-security yum --enablerepo=updates-testing --advisory=FEDORA-2013-1932 update
Created attachment 694487 [details] output of dmesg, /var/log/messages, .xsessions-errors First of all: Yesterday I completely reinstalled F18 from DVD and applied all updates. Also I deleted my home directory, so that all settings are 100% recreated - even if I have to reconfigure all. Then I installed the packages from that advisory and rebooted the machine. But problem still occurs. I attached the output of dmesg, /var/log/messages and .xsession-errors. The 'SystemTimeZones: ktimezoned initialize() D-Bus call failed' entry is still in .xsession-errors. In dmesg/messages I saw, that there is a Stack Trace, everytime the problem appears. In case that the system runs normal, the Stack Trace isn't there. If you are wondering, why I use the kernel, that was shipped with the DVD: Bug #907609 prevents me from using the latest one (TV card not working any more). I also saw that when I have this problem, other non-KDE applications are affected too. E. g. if I right-click to a link in FireFox, that application freezes. I also checked (before) I started Kaffeine, that '/etc/localtime' exists (is a symlink to /usr/share/zoneinfo/Europe/Berlin). I also run the 'qdbus org.kde.kded /kded org.kde.kded.loadModule ktimezoned' command. This is the output when the problem occours: Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: 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. And this is the output when the system runs fine: Cannot find 'org.kde.kded.loadModule' in object /kded at org.kde.kded
seems kded4 isn't running or crashed for you. that's not good. And, when you encounter problems, your dbus session isn't responding. dbus not responding or hanging would indeed cause your system to appear to freeze.
At the moments where the system runs fine (like at the moment, it's up for almost 4h without any problems), the pdbus command sill says: # qdbus org.kde.kded /kded org.kde.kded.loadModule ktimezoned Cannot find 'org.kde.kded.loadModule' in object /kded at org.kde.kded But kded4 is running: # ps axf | grep kded4 845 ? Sl 0:01 kded4 Is there anything else I can provide for debugging?
During the last days, it seems for me, that this problem is only appearing, when I start some KDE applications, like Kaffeine, very soon after logging in (booting). If the system is up for some time and I open Kaffeine, I don't had the hanging KDE issue, it seems.
I was about to comment earier too, that problems seem to occur shortly after you mention using kaffeine. you mentioned "some KDE applications", what others besides kaffeine triggers this?
I had this with kmail too. But I meanwhile migrated to Thunderbird, because my system freezes so often (mostly the first after startup is opening my mails). After I had reinstalled F18, I haven't installed/configured kde-pim any more. So I can't test this one any more.
I just wanted to give feedback, that with all updates (18.02.2012), the problem is still there. And even without starting Kaffeine. Sometimes I only had thunderbird and firefox running. And the haning appears, when right-clicking to something in firefox, too.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.