Bug 232364

In XFCE the situation is the same.

Can you please try to set layouts with setxkbmap and see if you have the same problem?

18.05.2010 06:19, Andriy Rysin пишет:
> https://bugs.kde.org/show_bug.cgi?id=232364
>
>
>
>
>
> --- Comment #2 from Andriy Rysin<arysin gmail com>   2010-05-18 04:19:21 ---
> Can you please try to set layouts with setxkbmap and see if you have the same
> problem?
>
>    
no it does'nt help
I set:
sudo setxkbmap -option grp:ctrl_shift -option grp_led:scroll -option 
lp3:ralt -layout us+typo,ru:2+typo


but my HP nx7400 then shows me again 2 leds on: scroll and caps :(

1. I am not sure why you use sudo for setxkbmap - you shouldn't
2. you should not merge layouts with "+", I am not sure why you need it but that's not recommended (and not supported) in x.org, more than that you can't do this with kxkb
3. to reset previous options you need to specify one more "-option"
4. in your first message you're saying you want "numlock" but you specify " -option grp_led:scroll"

so try this:
setxkbmap -layout us,ru -option -option grp:ctrl_shift_toggle,grp_led:scroll,lp3:ralt

If that works I'd suggest to wipe out your kxkbrc file and reconfigure kxkb from scratch. If that does not help please attach your new kxkbrc file here.

Dear Andriy.

Thank you much!
I removed kxkbrc file, reconfigured x11-xkb-utils & xxkb
and after
$setxkbmap -option -option grp:ctrl_shift_toggle -option 
grp_led:num,lp3:ralt,misc:typo -layout us,ru
my led indicators work properly
(it looks like the main mistake was in us+typo,ru:2+typo — it does not 
work any more)


19.05.2010 05:08, Andriy Rysin пишет:
> https://bugs.kde.org/show_bug.cgi?id=232364
>
>
>
>
>
> --- Comment #4 from Andriy Rysin<arysin gmail com>   2010-05-19 03:08:09 ---
> 1. I am not sure why you use sudo for setxkbmap - you shouldn't
> 2. you should not merge layouts with "+", I am not sure why you need it but
> that's not recommended (and not supported) in x.org, more than that you can't
> do this with kxkb
> 3. to reset previous options you need to specify one more "-option"
> 4. in your first message you're saying you want "numlock" but you specify "
> -option grp_led:scroll"
>    
num for my laptop of course

> so try this:
> setxkbmap -layout us,ru -option -option
> grp:ctrl_shift_toggle,grp_led:scroll,lp3:ralt
>
> If that works I'd suggest to wipe out your kxkbrc file and reconfigure kxkb
> from scratch. If that does not help please attach your new kxkbrc file here.
>
>

So is it working property with kxkb and we can close this bug?

Dear Andriy.

But leds do smth strange anyway…
They (two) became on without my participation, spontaniously.
Usualy it happens in firefox.

$ cat /home/jes/.kde/share/config/kxkbrc
[Layout]
DisplayNames=us,ru
IndicatorOnly=false
LayoutList=us,ru
Model=pc105
Options=grp:ctrl_shift_toggle,grp_led:num,lp3:ralt,compose:menu,misc:typo,terminate:ctrl_alt_bksp,lv3:ralt_switch,grp:rshift_toggle
ResetOldOptions=true
ShowFlag=false
ShowSingle=false
SwitchMode=WinClass
Use=true

End layout of keyboards switch do not obey properly to my switching — 
only from 2nd or 3rd time.

19.05.2010 05:08, Andriy Rysin пишет:
> https://bugs.kde.org/show_bug.cgi?id=232364
>
>
>
>
>
> --- Comment #4 from Andriy Rysin<arysin gmail com>   2010-05-19 03:08:09 ---
> 1. I am not sure why you use sudo for setxkbmap - you shouldn't
> 2. you should not merge layouts with "+", I am not sure why you need it but
> that's not recommended (and not supported) in x.org, more than that you can't
> do this with kxkb
> 3. to reset previous options you need to specify one more "-option"
> 4. in your first message you're saying you want "numlock" but you specify "
> -option grp_led:scroll"
>
> so try this:
> setxkbmap -layout us,ru -option -option
> grp:ctrl_shift_toggle,grp_led:scroll,lp3:ralt
>
> If that works I'd suggest to wipe out your kxkbrc file and reconfigure kxkb
> from scratch. If that does not help please attach your new kxkbrc file here.
>
>

Do you by any chance have .Xmodmap file in your home?

And let me reiterate: if you run 
setxkbmap -layout us,ru -option grp:ctrl_shift_toggle,grp_led:num,lp3:ralt,compose:menu,misc:typo
then leds work correctly, but if you start kxkb they don't?

20.05.2010 05:34, Andriy Rysin пишет:
> https://bugs.kde.org/show_bug.cgi?id=232364
>
>
>
>
>
> --- Comment #8 from Andriy Rysin<arysin gmail com>   2010-05-20 03:34:56 ---
> Do you by any chance have .Xmodmap file in your home?
>
>    
No, I don't.

> And let me reiterate: if you run
> setxkbmap -layout us,ru -option
> grp:ctrl_shift_toggle,grp_led:num,lp3:ralt,compose:menu,misc:typo
> then leds work correctly, but if you start kxkb they don't?
>    

Work correctly if windows of thunderbird or firefox or stardict f.e. are 
closed or minimized — thus I use only terminal.
If I open that window, leds suddenly (sometimes) become lighted on.
I can'nt find any logic in this, besides, sometimes I can not turn 
lightened leds off the
first time even with the help of setxkbmap command, but only by several 
manipulation with rshift_toggle + caps (If 2 leds — caps & num are 
turned on)

I don't think I'd be able to help here, if numlock depends on some programs to be minimized that does not seems like a problem with keyboard layout switcher. Plus earlier you said that in XFCE the situation is the same which makes it non-kxkb problem (unless you start kxkb in XFCE).

Dear Andtiy!

It seems everything has began work properly after I've deleted ledd 
script from processes (/etc/init.d/ledd) %/

22.05.2010 16:55, Andriy Rysin пишет:
> https://bugs.kde.org/show_bug.cgi?id=232364
>
>
>
>
>
> --- Comment #10 from Andriy Rysin<arysin gmail com>   2010-05-22 14:55:25 ---
> I don't think I'd be able to help here, if numlock depends on some programs to
> be minimized that does not seems like a problem with keyboard layout switcher.
> Plus earlier you said that in XFCE the situation is the same which makes it
> non-kxkb problem (unless you start kxkb in XFCE).
>
>

That's really good news, thanks for finding the source problem!
So shall we close this bug report?

24.05.2010 16:58, Andriy Rysin пишет:
> https://bugs.kde.org/show_bug.cgi?id=232364
>
>
>
>
>
> --- Comment #12 from Andriy Rysin<arysin gmail com>   2010-05-24 14:57:59 ---
> That's really good news, thanks for finding the source problem!
> So shall we close this bug report?
>
>    
yes, surely

Marking as resolved as it was a ledd problem.