Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 370521

Summary: RHEL51:PPORT: Localization issue with French,German and Spanish at firstboot
Product: Red Hat Enterprise Linux 5 Reporter: Rezwanul Kabir <rezwanul_kabir>
Component: firstbootAssignee: Chris Lumens <clumens>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5.1CC: jfeeney
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: 2008-01-31 23:35:46 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:
Attachments:
Description Flags
Call trace on firstboot none

Description Rezwanul Kabir 2007-11-07 22:33:19 UTC
Description of problem:
On RHEL5.1, at firstboot, if the user chooses any of the above mentioned 
languages and press "Forward", a Call Trace ( as attached) appears. If the 
user chooses to continue, when he reaches the "TimeZone" screen and chooses a 
timezone and press "Forward" , he is continually presented with an error 
message saying that "root password must be at least 6 characters in length"

Version-Release number of selected component (if applicable):
firstboot-1.4.27.3-1.el5

How reproducible:
Always

Steps to Reproduce:
1.Install RHEL5.1
2.On firsboot choose any of the above 3 languages
3.
  
Actual results:

Error messages

Expected results:

Should be able to choose any languages.

Additional info:

Comment 1 Rezwanul Kabir 2007-11-07 22:33:19 UTC
Created attachment 250971 [details]
Call trace on firstboot

Comment 2 RHEL Program Management 2007-11-07 23:04:42 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 3 Chris Lumens 2008-01-31 23:35:46 UTC
I am closing this bug as WONTFIX, as I am proposing removing the language
selection screen entirely due to the fact that it is perpetually broken (as this
and other bugs attest) and that it is entirely misleading in what it
accomplishes.  Please refer to bug 431143 for tracking that resolution.

Comment 4 Larry Troan 2008-02-07 19:01:27 UTC
On Thu, 2008-02-07 at 10:22 -0600, Rezwanul_Kabir wrote:
> Hi Larry
> 
> This  bug is being set to WON'T FIX and refers to bug 431143 for 
> explanation. I am writing to inform that it's unacceptable to Dell. 
> Localization at firstboot is very important to us. This is used by
> our users in different regions ( some of them knows/understands little 
> English) to do initial setup. Accepting License Agreement,setting root 
> password,subscribing to RHN all these are offered at firstboot and users
> need to be able to make conscious decisions at this time.
> 
> The developer assigned to this bug wants to eliminate language screen all 
> together at firstboot for the following reasons:
> 
>  1) The code is complex and opaque 
>  2) The installation might not have included other required language
      packages and so applications like Firefox,OpenOffice etc. may not be
      localized. In that case, firstboot language screen offers partial 
      solution.
> 
>  #1 is not our concern 
>  For #2, we are making sure during factory install that all required
>  language packages are installed. So, it doesn't apply to us.
> 
>   As I have discussed during our last weekly call, the resolution to
>   this bug is important to us. I have discussed this with John Hull
>   and have added him to this thread.
> 
>    Thanks.. 
>       --rez

Comment 5 Larry Troan 2008-02-07 19:11:01 UTC
Have asked SEG if the current Red Hat position (as listed above) is acceptable
to them long term.

Comment 7 Larry Troan 2008-02-13 13:08:35 UTC
Dell believes that Red Hat is in the best position to fix this code.

Per RHEL meeting on 2/12/08, this function is poorly implemented and not easily
fixable. We can assess a different approach in a future update but it will not
be available in 5.2. 

Therefore closing as WONTFIX for 5.2. Ken R. has agreed to explain the rationale
if necessary.