Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 225155

Summary: On UTF-8 locale russian capital letters do not appear but small do when CapsLock is switched on in native console
Product: Gentoo Linux Reporter: eveler <eveler555>
Component: [OLD] UnspecifiedAssignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Severity: normal CC: base-system, maxkill
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Package list:
Runtime testing required: ---

Description eveler 2008-06-06 23:22:51 UTC
This is my system config:
cat /etc/conf.d/consolefont

cat /etc/conf.d/keymaps
KEYMAP="-u ru"

Portage (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.24-gentoo-r8 x86_64)

In native console russian capital letters do not appear but small do when CapsLock is switched on. However when Shift holded all is ok. So there is no matter CapsLock is switched on or off. 
But in xterm or konsole all is goes rigth.

cat /etc/X11/xorg.conf
Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbModel" "pc105"
        Option      "XkbLayout" "us,ru"
        Option      "XkbVariant" ",winkeys"
        Option      "XkbOptions" "grp:ctrl_shift_toggle,grp_led:scroll"

Reproducible: Always

Steps to Reproduce:
1.switch locale (Cttl+Shift)
2.switch CapsLock
3.type a text

Actual Results:  

Expected Results:  

English text appear as expected
Comment 1 Rémi Cardona (RETIRED) gentoo-dev 2009-06-24 06:47:00 UTC
Sorry for letting this bug slip through the cracks.

I assume you were using xorg-server 1.3 when you opened this bug. Can you still reproduce this bug with newer versions of xorg-server and xkeyboard-config? Please don't hesitate to reopen this bug report if you can still reproduce the issue.

Comment 2 Maxim Ganetsky 2009-09-03 15:35:46 UTC
This bug still can be reproduced on fully updated stable branch.

Note that original bug report states that problems are present only *without* X in *pure* console; in virtual terminals under X (e.g. xterm or konsole) everything works correctly.
Comment 3 Rémi Cardona (RETIRED) gentoo-dev 2009-09-03 21:10:39 UTC
What goes on outside X is not my area of expertise, please get in touch with the kernel team as they are the ones responsible for the text console.

Comment 4 Maxim Ganetsky 2009-09-03 21:47:29 UTC
I understand. In fact I don't know why this bug was assigned to the X packagers in the first place.

Can you reassign this bug to the kernel team? I can't change its status.
Comment 5 Rémi Cardona (RETIRED) gentoo-dev 2009-09-04 07:54:46 UTC
Gladly :)
Comment 6 Rémi Cardona (RETIRED) gentoo-dev 2009-09-04 07:55:34 UTC
@Kernel team, this bug was mistriaged as an X bug while this is a console bug.

Cheers :)
Comment 7 Mike Pagano gentoo-dev 2009-09-04 12:12:58 UTC
Adding base-system herd.  Is this kernel or a sys-apps/kbd issue?

Can you tell us what version of sys-apps/kbd you are running?
Comment 8 Maxim Ganetsky 2009-09-04 12:48:59 UTC
I have 1.13-r1 version of sys-apps/kbd and 2.6.30-r5 kernel (gentoo-sources).
I use stable branch.
Comment 9 George Kadianakis (RETIRED) gentoo-dev 2009-09-19 19:27:00 UTC
Hey there,

I'd like you to - after keeping a backup of your /usr/share/X11/xkb/symbols/ru -
change "key <LatQ> { [ Cyrillic_ya, Cyrillic_YA ] };" in there, to "key <AD01> { [ Cyrillic_ya, Cyrillic_YA ] };".

Do check this bug report out:

Thanks :)
Comment 10 Maxim Ganetsky 2009-09-19 20:13:50 UTC
I guess I need to reiterate that this bug is *NOT* related to X. In X virtual terminals everything works correctly.
Comment 11 Mike Pagano gentoo-dev 2009-11-22 13:54:23 UTC
I'm at a loss here and don't really know where to point you to go, here.  Have you had any progress on this on your own?
Comment 12 Maxim Ganetsky 2009-11-23 00:20:11 UTC
No. But the bug is still here on stable Gentoo with latest updates.
Comment 13 Mike Pagano gentoo-dev 2010-02-16 16:35:24 UTC
My suggestion is to talk to others who use the charset you do and see if they can help you troubleshoot this issue.  Sorry I could not be more helpful