Bug 196896 - Plasma gets unresponsive after some time (high cpu usage) (dbus/hal related(?))
Summary: Plasma gets unresponsive after some time (high cpu usage) (dbus/hal related(?))
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-17 18:18 UTC by nigeldclegg
Modified: 2012-05-28 22:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nigeldclegg 2009-06-17 18:18:41 UTC
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.
Comment 1 Dario Andres 2009-06-17 22:07:23 UTC
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
Comment 2 nigeldclegg 2009-06-18 17:59:38 UTC
(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
Comment 3 nigeldclegg 2009-06-18 18:09:13 UTC
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.
Comment 4 nigeldclegg 2009-06-18 18:12:28 UTC
(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
Comment 5 Aaron J. Seigo 2009-06-23 23:45:42 UTC
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.
Comment 6 nigeldclegg 2009-06-24 12:26:57 UTC
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.
Comment 7 nigeldclegg 2009-07-04 19:08:15 UTC
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.
Comment 8 nigeldclegg 2009-07-04 19:34:34 UTC
I have also discovered that killing udevd makes the cpu run as normal.
Comment 9 Dario Andres 2009-07-04 23:50:08 UTC
Verified-Waitingforinfo is not a valid combination. Reopening
Comment 10 Aaron J. Seigo 2010-05-25 23:45:56 UTC
answers to the questions in comment #5 are required to be able to do anything with this report.
Comment 11 Myriam Schweingruber 2012-05-28 22:25:47 UTC
Closing for lack of feedback.