Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 153118

Summary: gdm and syslogd taking almost all cpu time.
Product: [Fedora] Fedora Reporter: Khem Raj <raj.khem>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-04 22:36:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Khem Raj 2005-04-01 17:46:27 UTC
Description of problem:

When system is rebooted after FC4 test 1 installation, it takes very  long time
to log in (magnitude of 20 -30 mins). The gdm screen comes up ok but when log in
and password are typed the screen goes blue and remains same for these 20-30
mins before gnome starts. 

Once started the application also take a long time to load. When terminal starts
and typing top on the terminal it shows,

gdm is taking 46% of CPU power
syslogd is taking another 52% of cpu power.

Version-Release number of selected component (if applicable):

How reproducible:

everytime system is rebooted.

Steps to Reproduce:
1.Install FC4 test1 3.90 and do a reboot.
Actual results:
Takes a long time to respond

Expected results:

Additional info:

Comment 1 Khem Raj 2005-04-04 22:36:23 UTC
Updating the gdm to gdm- and syslogd to sysklogd-1.4.1-28
solved the problem.