Bug 279377

Summary:	dbus-daemon consumes 100% cpu after a few days
Product:	[I don't know] kde	Reporter:	Bill Metzenthen <billm>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	billm, cfeck
Priority:	NOR	Keywords:	usability
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Bill Metzenthen 2011-08-04 12:42:46 UTC

Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

The session bus dbus-daemon consumes 100% of one core starting about a week after a fresh boot.

There is a suggestion (http://us.generation-nt.com/answer/bug-630002-dbus-dbus-daemon-consumes-40-cpu-amd64-help-203742362.html) that this may be related to " a KDE process that leaks D-Bus connections".

/proc/ID/fd shows that dbus-daemon has 1024 file descriptors, most of them sockets.

This is on Kubuntu 11.04

KDE applications such as kmail, knode, etc become unusable when dbus-daemon gets to this state.

Which application(s) are likely to be causing the problem?  Is there any way other than re-booting to get dbus-daemon to resume functioning correctly?


Reproducible: Always

Steps to Reproduce:
Just run KDE for a few days.


Actual Results:  
dbus-daemon stops some KDE applications from functioning correctly

Expected Results:  
All applications should function as normal

Comment 1 Christoph Feck 2011-08-04 21:42:23 UTC

Can you check if this is fixed in KDE 4.7? It is probably caused by Software Update Notification tools, which are provided by your distribution. See bug 261180.

*** This bug has been marked as a duplicate of bug 261180 ***

Comment 2 Bill Metzenthen 2011-08-06 02:28:54 UTC

I will check with 4.7, but first I will gather a little more data with the current installation.  At the moment I have an uptime of one and a half days and the number of descriptors in use by dbus-daemon has peaked at less than 100.

Because it takes several days before dbus-daemon finally stops the KDE processes from working properly, it could be a couple of weeks before I say whether or not 4.7 makes a difference.