Bug 60157 - Severe penalties for mistyping
Summary: Severe penalties for mistyping
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-21 00:18 UTC by Michal Jaegermann
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-02-22 00:45:45 UTC
Embargoed:

Attachments (Terms of Use)
Traceback from anaconda expresing a dislike to a password input (39.89 KB, text/plain)
2002-02-22 00:45 UTC, Michal Jaegermann 		no flags Details
View All

Description Michal Jaegermann 2002-02-21 00:18:33 UTC 
Description of Problem:

On a password setup screen if "Passwords do not match" shows up and
one will hit "Next" button anyway (easy to do by a mistake) the whole
anaconda blows up without giving a chance for corrections
Comment 1 Jeremy Katz 2002-02-21 00:37:48 UTC 
Do you get a traceback?  I can't reproduce here (clicking on the insensitive
next button correctly does nothing)
Comment 2 Michal Jaegermann 2002-02-21 06:08:29 UTC 
No, I do not have a traceback.  The thing was instantly rebooting and the
machine on which this was happening consistently is not here.  I will try
to do some careful catch in a day or two if you cannot reproduce.
Comment 3 Michal Jaegermann 2002-02-22 00:43:08 UTC 
Ok, here is a traceback (attached).  Of course when I am trying to reproduce
it is not that easy as opposed to a normal installation when it was happening
every time I hit a wrong key.  I am not sure what one has type precisely
for this to happen but "goofing around" on a password screen for a while
surely triggered it again.
Comment 4 Michal Jaegermann 2002-02-22 00:45:40 UTC 
Created attachment 46344 [details]
Traceback from anaconda expresing a dislike to a password input
Comment 5 Jeremy Katz 2002-02-22 21:41:05 UTC 
Dupe of another bug already fixed in CVS
Note You need to log in before you can comment on or make changes to this bug.