[Hardy][regression]"Use keyboard LED to show alternative layout" does not work

Omid
Thank you for taking the time to report this problem.

Could you please describe the steps in a little more detail,
that can be taken to reproduce the problem.

Your welcome, we are here to share ;)

How can i describe steps?

It's working fine before upgrading from Gutsy to Hardy, after upgrading it doesn't work. Checked that it was marked in layout preferences, try to remove the mark, then close the windows and again mark it, but nothing happened!

If I should dump something here, please tell me what is that command.

I still have this problem!

ii gnome-control-center 1:2.21.90-0ubuntu3 utilities to configure the GNOME desktop

The bug still exists in current Hardy.

How to reproduce: go to Menu -> System -> Preferences -> Keyboard.
On the layout tab add a second layout. Uncheck "Separate layout for each window".
Open "Layout Options...", and select a way for "Layout switching".
Also make sure that layout switching works for you (see bug #196277).
Also select any option for "Use keyboard LED to show alternative layouts."

Now if you switch your layout, the selected LED's should go on/off to indicate the layout.
But they do not. This is a regression, as it worked in Feisty and Gutsy.

Appropriate section of xorg.conf:

Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "kbd"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "hu"
        Option "XkbVariant" "102_qwertz_dot_nodead"
        Option "XkbOptions" "lv3:ralt_switch"
EndSection

How could I supply more information on this?

I confirm this bug. I've submitted the same bug recently:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/225453

Everything the same as described by Garbor Czigola. Ubuntu Hardy with all the updates installed.

Workaround:
-------------------
The problem can be solved by manually editing x.org.conf :

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "pl,ua(unicode)"
 Option "XkbOptions" "grp:lwin_toggle,grp_led:num,lv3:ralt_switch"
EndSection

grp_led:num - for Numlock, grp_led:scroll for ScrollLock and grp_led:caps for CapsLock. It now works for me. But it's not good that I now can't change keyboard LED behavior from gnome-control-center.

Another problem (maybe related to this one) is when I press NumLock key on my laptop, the LED doesn't turn on (but the numpad changes its behavior).

@noddeat:
What "xmodmap -pm" says about your NumLock? I'm not sure but you can read this article:
http://linuxtechie.wordpress.com/2008/04/07/getting-scroll-lock-to-work-in-ubuntu/

$ xmodmap -pm
xmodmap: up to 3 keys per modifier, (keycodes in parentheses):

shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1 Alt_L (0x40), Meta_L (0x9c)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x7f), Hyper_L (0x80)
mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x71), ISO_Level3_Shift (0x7c)

Since I don't have a ScrollLock LED on my laptop, everything is ok there, the article will not help :(.

The bug is still here (Hardy x64)

According to Gnome bugtracker (http://bugzilla.gnome.org/show_bug.cgi?id=518156), this is not a Gnome but an Xorg problem. Another bug (https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/194526) has a proper package chosen, so I set this bug as a duplicate of that one.