Sometimes when resuming from sleep (every second sleep after a reboot, in my last tests), the process named kde4 starts doing a lot of IO and its memory usage ("Memory" column in ksysguard) goes from less than 50 Mo to more than 800 Mo (then the IO stops). After that some actions are very slow (several dozen seconds or minutes) or even impossible: * changing screen brightness with Fn keys or systray applet * all actions in "Start menu" > Exit * right click on a file in Dolphin * right click > "Open the link" in Konsole * starting KRDC * "Save as..." in Firefox (KDE component) [UI labels back-translated from French, sorry for any inaccuracy] I did diffs on the output of lsof when kde4 does all this IO and I didn't see anything interesting. I'm using kdebase4-common-4.14.3-1.mga5. Reproducible: Steps to Reproduce:
CC: (none) => balcaen.john, marja11Assignee: bugsquad => mageia
Hello, I don't know if I have the same problem, but for a few days (1 week or 2, maybe since the last KDE update?), after a suspend, and some time, the disk access of KDE become very slow (a right click in Konqueror file manager or Dolphin can take several minutes before the menu appear). I had not the problem before. I'm also using kdebase4-common-4.14.3-1.mga5.
CC: (none) => mageia
An interesting fact is that when you "su" to another user, the KDE apps are working fine (correct disk access time).
I cannot reproduce the bug anymore. Did an update fix it? I didn't notice any update on KDE packages but perhaps I missed one. If anyone solved this on purpose then thanks a lot! Otherwise the most significant change in my config is that my VGA output seems dead so I stopped using it (I use my HDMI output instead). I have no idea whether this could be related.
(In reply to Johan Grande from comment #3) > I cannot reproduce the bug anymore. Thanks for the feedback, Johan :-) > > Did an update fix it? I didn't notice any update on KDE packages but perhaps > I missed one. If anyone solved this on purpose then thanks a lot! Other packages can affect KDE, like the recent kernel and libx11 updates. > > Otherwise the most significant change in my config is that my VGA output > seems dead so I stopped using it (I use my HDMI output instead). I have no > idea whether this could be related. Nor do I :-) @ Bertrand How are things for you? Does everything work fine now?
(In reply to Marja van Waes from comment #4) > > @ Bertrand > > How are things for you? Does everything work fine now? Indeed, I did not meet the problem for a long time... But, as it was difficult to reproduce (I had not the bug each time), I am not entirely sure that the bug is really gone...
(In reply to Johan Grande from comment #3) > I cannot reproduce the bug anymore. (In reply to Bertrand Marne from comment #5) > I did not meet the problem for a long time... But, as it was > difficult to reproduce (I had not the bug each time), I am not entirely sure > that the bug is really gone... Thanks for reporting back :-) Assuming a non-KDE update fixed it, and closing this bug as fixed. Please reopen if the issue reoccurs, though!
Status: NEW => RESOLVEDResolution: (none) => FIXED