Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 133952 - Wrong keyboard layout in firstboot
Wrong keyboard layout in firstboot
Status: CLOSED DUPLICATE of bug 100686
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhgb (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Veillard
Depends On:
  Show dependency treegraph
Reported: 2004-09-28 13:02 EDT by Bernd Bartmann
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:05:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bernd Bartmann 2004-09-28 13:02:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)

Description of problem:
Looks like bug #100686 (which I can't reopen) seems to have appeared
again in RHES4 Beta1.

Symptoms: Fresh install, German locale, added a local user in
firstboot but could not log on as this user because the keyboard
layout was not correctly set in firstboot.

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

How reproducible:

Steps to Reproduce:
1. test the keyboard layout in firstboot

Additional info:
Comment 1 Daniel Veillard 2004-09-28 13:32:34 EDT
what version of rhgb do you see ?

Comment 2 Bernd Bartmann 2004-09-28 13:40:33 EDT
The one that comes with RHES4 Beta1: rhgb-0.11.2-8

Comment 3 Daniel Veillard 2004-09-28 13:48:52 EDT
 Well 100686 is fixed in 0.12.6 and rhgb-0.11.2-8 doesn't have the fix,
so it will be only in the next beta, so it's a duplicate...


*** This bug has been marked as a duplicate of 100686 ***
Comment 4 Red Hat Bugzilla 2006-02-21 14:05:58 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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