Bug 612459 - have to select user twice after rejecting timed login in gdm
Summary: have to select user twice after rejecting timed login in gdm
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gdm
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: jmccann
QA Contact: desktop-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-08 09:41 UTC by Vladimir Benes
Modified: 2015-01-14 23:25 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2010-11-10 20:28:08 UTC

Attachments (Terms of Use)

Description Vladimir Benes 2010-07-08 09:41:47 UTC
Description of problem:
after rejecting timed login in gdm I have to select user twice as after first attempt gdm goes back into user selection list

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

How reproducible:

Steps to Reproduce:
1.enable timed login in custom.conf set time to approx 10 second to be able to reject it
2.go into gdm and reject timed login
3.select user
Actual results:
back in user selection list

Expected results:
password text field should be prompted 

Additional info:

Comment 2 Ray Strode [halfline] 2010-07-14 03:17:36 UTC
So i looked into this this evening, and it seems a lot more dire than comment 0.  I don't know if that's because gdm has been rev'd since that comment or if it's just a timing issue, but on my laptop timed login doesn't seem to work at all after cancel. It gets into a sort of deranged state where you can do anything anymore.

There were a few bugs that together made this happen.  I've corrected them and it should be better in gdm-2.30.4-7.el6.

marking MODIFIED and moving from exception to blocker given how much more serious the bug seems to be than I originally thought.

Comment 5 Radek Lat 2010-08-19 09:12:05 UTC
Tested and Verified on gdm-2.30.4-21.el6.x86_64, problem seems to be no longer present.

Comment 6 releng-rhel@redhat.com 2010-11-10 20:28:08 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.

Note You need to log in before you can comment on or make changes to this bug.