Version: (using KDE 4.2.4) OS: Linux Installed from: Ubuntu Packages Initially I can still switch between programmes using alt-tab (as long as I don't leave it too long) but the taskbar and desktop are not responsive. If I kill plasma then start it again everything works for 10-15 minutes again, then I would need to kill and restart plasma again. If I don't kill plasma, eventually nothing responds including the power button. In system monitor, it seems to be when Memory gets to around 600/993mb. The swap reads 0b/0b.
This could be related to graphics drivers or the SystemTray(/other plasma components) leaking memory. Those errors should be fixed onb KDE4.3 In the meanwhile, what is your graphics card/drivers ? What widgets are you using in Plasma ? Any non-official one ? Thanks
(In reply to comment #1) > This could be related to graphics drivers or the SystemTray(/other plasma > components) leaking memory. Those errors should be fixed onb KDE4.3 > > In the meanwhile, what is your graphics card/drivers ? What widgets are you > using in Plasma ? Any non-official one ? > Thanks Hi, It was a full new installation from a newly downloaded CD after completing an integrity check. I have found if I kill dbus-daemon--system the problem stops. What do I type into Konsole to get the information you want? Thanks
I have just experimented and found if I kill hald instead of the dbus-daemon the problem stops and the cpu behaves normally dropping to 3% when idle.
(In reply to comment #3) > I have just experimented and found if I kill hald instead of the dbus-daemon > the problem stops and the cpu behaves normally dropping to 3% when idle. I have just restarted hald and the cpu runs at 29% and steadily increasing when idle
if you start HAL without Plasma running, does it show a similar problem? if you start Plasma without HAL, remove the device notifier, app launcher and/or battery monitor and then start HAL do things work better? evidently HAL is doing something amazingly incorrect on that system, but it would be good to know _what_ so we can determine if it is indeed a HAL bug or something we can work around in plasma or solid.
Hi, Sorry... I gave up trying to sort it and did another fresh install, updated and still had the problem until the next morning when it was suddenly sorted. Thanks for your help. I am now a happy Linux user again.
Nooooo! It's doing the same thing again suddenly. If I kill hald it's ok. If I kill dbus-daemon (messagebus) it's ok. I'll stick with it this time to try to sort it so please tell me what you need.
I have also discovered that killing udevd makes the cpu run as normal.
Verified-Waitingforinfo is not a valid combination. Reopening
answers to the questions in comment #5 are required to be able to do anything with this report.
Closing for lack of feedback.