Bug 633496

Summary: dbus-daemon may consume 100% CPU
Product: [Fedora] Fedora Reporter: Steve Tyler <stephent98>
Component: dbusAssignee: David Zeuthen <davidz>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: cdennett, davidz, lpoetter, mads, mclasen, walters
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 12:54:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steve Tyler 2010-09-13 20:34:42 UTC
Description of problem:
dbus-daemon consumes 100% CPU for about 90 seconds if selinux is disabled and the SELinux Troubleshooter GUI is started and then exited by clicking the Close button.

Version-Release number of selected component (if applicable):
dbus-1.2.24-1.fc13.x86_64
setroubleshoot-2.2.96-1.fc13.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Disable selinux with the SELinux Management GUI app.
2. Reboot.
3. Run "top" in a terminal window.
4. Start the SELinux Troubleshooter GUI app.
(It can also be invoked from a command line with "sealert -b".)
5. A warning box is displayed:
"SELinux not enabled, sealert will not run on non SELinux systems"
6. Click the Close button in the warning box.
  
Actual results:
SELinux Troubleshooter quits.
dbus-daemon immediately begins consuming 100% CPU
and continues that way for about 90 seconds.

Expected results:
dbus-daemon does not consume 100% CPU.

Additional info:
Noted while testing fix for:
Bug 568541 - setroubleshoot GUI quits without explanation when selinux disabled

Reported here by robatino:
"Bug 568541  is NOT fixed - after disabling SELinux, rebooting, and running "/usr/bin/sealert -b", I just get the prompt back (eventually). In addition, dbus-daemon uses 100% CPU for a while."
https://admin.fedoraproject.org/updates/setroubleshoot-2.2.96-1.fc13

Comment 1 Bug Zapper 2011-05-31 13:36:20 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Steve Tyler 2011-05-31 17:21:12 UTC
Fixed in F15:
dbus-1.4.6-4.fc15.x86_64
setroubleshoot-3.0.31-1.fc15.x86_64

Comment 3 Bug Zapper 2011-06-28 12:54:28 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Thank you for reporting this bug and we are sorry it could not be fixed.