This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 446345 - firstboot does not allow input of english (latin) characters when using russian locale ru_RU.UTF8
firstboot does not allow input of english (latin) characters when using russi...
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: firstboot (Show other bugs)
9
All Linux
low Severity medium
: ---
: ---
Assigned To: Chris Lumens
Fedora Extras Quality Assurance
:
: 446564 446917 453228 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-14 03:48 EDT by Alex Kanavin
Modified: 2008-07-31 15:35 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-31 15:35:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alex Kanavin 2008-05-14 03:48:36 EDT
Description of problem:
When choosing russian language and keyboard during Fedora installation, firstboot is using that keyboard 
layout as a default, and provides no way to input latin characters (toggle-layout key combination, which is 
pressing both shift keys, does not work either). This results in being unable to create a user, or do any 
other configuration which involves text input. I believe users from Greece, Ukraine or any country with 
cyrillic alphabet will have a similar problem.
Comment 1 Chris Lumens 2008-05-15 10:55:07 EDT
*** Bug 446564 has been marked as a duplicate of this bug. ***
Comment 2 Chris Lumens 2008-05-16 12:51:27 EDT
*** Bug 446917 has been marked as a duplicate of this bug. ***
Comment 3 Chris Lumens 2008-07-31 13:34:04 EDT
*** Bug 453228 has been marked as a duplicate of this bug. ***
Comment 4 Chris Lumens 2008-07-31 15:35:57 EDT
This will be fixed in the next build of firstboot for Rawhide/F10.

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