Bug 722697 - [ru_RU] Russian keyboard cannot enter control characters
Summary: [ru_RU] Russian keyboard cannot enter control characters
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xkeyboard-config
Version: 14
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-16 17:56 UTC by Hidden
Modified: 2012-06-26 06:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-26 06:10:37 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Hidden 2011-07-16 17:56:27 UTC 
Description of problem:
When russian keyboard is used in GUI environment, control symbols cannot be entered.

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

How reproducible:
Always

Steps to Reproduce:
1. Select Russian keyboard for system
2. Open GUI terminal emulator
3. run 'sort'
4. Enter some text and press Ctrl+D
  
Actual results:
Russian letter 'в' is typed.

Expected results:
^D sequence is typed, and keyboard input to sort finished.

Additional info:
Applicable to any terminal emulator supplied, doesn;t affect virtual consoles and GUI apps like firefox.
Comment 1 Jens Petersen 2011-11-09 06:53:24 UTC 
Is this still the case for newer releases?
Comment 2 Jens Petersen 2012-02-10 02:13:24 UTC 
Probably one needs to switch to English layout to input control characters?
Or is this a regression?
Comment 3 Akira TAGOH 2012-06-06 08:24:24 UTC 
Any updates? please try on the latest release to check if this still persists.
Comment 4 Peter Hutterer 2012-06-26 06:10:37 UTC 
This bug was filed against Fedora 14 which is now EOL. Please re-open this bug if you still experience this issue with one of the currently suppported versions of Fedora. Don't forget to update the version field if you do so.
Note You need to log in before you can comment on or make changes to this bug.