Bug 10224 - Incorrect cyrillic ctrl+alt+f5
Summary: Incorrect cyrillic ctrl+alt+f5
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-22 17:00 CEST by Alex Loginov
Modified: 2014-12-18 19:41 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Illustration (121.82 KB, image/jpeg)
2013-05-22 17:05 CEST, Alex Loginov 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alex Loginov 2013-05-22 17:00:43 CEST 
Description of problem: If to press ctrl+alt+f5 and to use Russian keyboard, then you can see ?????? instead symbols.
How reproducible: always
Picture is in attachment.

Reproducible: 

Steps to Reproduce:
Comment 1 Alex Loginov 2013-05-22 17:05:19 CEST 
Created attachment 4024 [details]
Illustration
Comment 2 Alex Loginov 2013-05-23 17:56:04 CEST 
Sollution:
[root@localhost ~]# loadkeys -u ru
or to add this command in /etc/rc.d/rc.local
Comment 3 Manuel Hiebel 2013-05-28 21:46:32 CEST 
were do you see that ? seems not the default shell
Comment 4 Alex Loginov 2013-05-28 22:00:07 CEST 
It's ctrl+alt+f5.
Comment 5 Manuel Hiebel 2013-05-28 22:03:11 CEST 
well default prompt looks not like that

Version: Cauldron => 3

Comment 6 Alex Loginov 2014-01-20 11:04:06 CET 
No problem in Mageia 4 RC, I looked in vmware-player.
Comment 7 Alex Loginov 2014-12-18 19:38:17 CET 
Hi, thanks for reporting this bug.
We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:WONTFIX

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 8 Sander Lepik 2014-12-18 19:41:55 CET 
Just a comment, better close such bugs as RESOLVED:OLD.

CC: (none) => mageia
Note You need to log in before you can comment on or make changes to this bug.