Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMatthias Schroder
2010-06-01 13:27:03 UTC
Description of problem: When the password file is big, and disable_user_list is false, gdm-simple-greeter uses 100% CPU for several minutes after startup
Version-Release number of selected component (if applicable): 2.28.2-5.el6.x86_64
How reproducible: 100%
Steps to Reproduce:
1. Use large password file
2. boot machine
3. watch gdm-simple-greeter hogging CPU
Actual results: gdm-simple-greeter hogs CPU
Expected results: CPU available for useful things
Additional info:
1) Setting disable_user_list to true (I had to search quite a bit to find that one) avoids the issue.
2) This could be related to https://bugzilla.redhat.com/show_bug.cgi?id=598145
3) Numbers: processing a ~22k password file takes 5 minutes :(
Comment 2RHEL Program Management
2010-06-07 16:07:47 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 3Ray Strode [halfline]
2010-06-11 13:58:26 UTC
Just an update here.
Jon has done considerable work making this quite fast upstream.
Comment 4Ray Strode [halfline]
2010-06-11 14:30:44 UTC
We should rebase to pull this in. Otherwise we're going to have a bunch of pointless patches in cvs that will make maintainability more difficult. The gnome-2-30 branch is all minor bugfixes and translation updates.
*** Bug 598145 has been marked as a duplicate of this bug. ***
Comment 8Ray Strode [halfline]
2010-06-29 19:22:28 UTC
Should be good to go.
Comment 10Matthias Schroder
2010-07-16 13:49:07 UTC
In beta 2 the time it takes for the simple-greeter is ok now. But the gdm-user-switch-applet still needs 1:45, and during that time I don't get the gnome-panel. I admit that the time has decreased significantly, but it is still quite long. And together with https://bugzilla.redhat.com/show_bug.cgi?id=610233 this becomes painful...
Please file a new bug for that. Can you attach gdb to the user switch applet during this time and interrupt it a few times to see where it is spending time? Thanks.
Tested with >40k password file on gdm-2.30.4-21.el6.x86_64. No CPU hogging. Moving to VERIFIED.
Comment 13releng-rhel@redhat.com
2010-11-10 20:27:44 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.