Welcome to awesome bug tracking system.

FS#476 - xxkb does not remember keyboard layout asociated with application in awesome 3.2

Attached to Project: awesome
Opened by Andrey Grez (grez) - Thursday, 19 March 2009, 22:12 GMT
Task Type Bug Report
Category Core
Status Unconfirmed
Assigned To No-one
Operating System Linux
Severity Low
Priority Normal
Reported Version 3.2
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 2
Private No


xxkb (keyboard layout switcher) does not remembers keyboard layout asociated with application in awesome 3.2

-start xxkb
-start two applications in different tags (in this example tag1:firefox, tag2:pidgin)
-go to firefox, switch layout to "En"
-go to pidgin, switch layout to "Ru"

expected behavior:
-go to firefox, check keyboard layout, it should be English.
-go to pidgin, check keyboard layout, it should be Russian.

actual behavior:
-both firefox and pidgin have Russian layout.

In awesome 3.1 ewerything was working great.

my .xxkbrc :
XXkb.controls.two_state: no
XXkb*label.text.1: En
XXkb*label.text.2: Ru
XXkb*label.text.3: Ua
XXkb.mainwindow.type: tray
XXkb.mainwindow.label.enable: yes
XXkb.mainwindow.enable: yes
XXkb.mainwindow.appicon: no
XXkb.mainwindow.geometry: 20x20+0+0
XXkb.mainwindow.in_tray: GNOME2
XXkb.mainwindow.label.background: black
XXkb.mainwindow.label.foreground: yellow
XXkb.mainwindow.label.font: -misc-*-r-*-13-*
XXkb.button.enable: no
This task depends upon

Comment by Andrei Thorp (garoth) - Friday, 20 March 2009, 00:47 GMT
Hmm. Agreed, I also started having this behaviour changing between Qwery + Dvorak. You must restart applications for the layout to change. To reiterate:

Start a term. Type something in qwerty.
Type "setxkbmap us dvorak"
Type something -- text comes out in qwerty layout, keybindings change to use dvorak.

This is very strange. I assumed that this was an X issue, but perhaps it is not.
Comment by Julien Danjou (jd) - Friday, 20 March 2009, 06:58 GMT
I don't see how it can be an swesome issue; bisection probably required for such a case.
Comment by Andrei Thorp (garoth) - Friday, 20 March 2009, 20:42 GMT
Did a bunch of checks between now and 1000 commits ago, and the behaviour is not fixed at any point. I personally blame an X update that may have co-incided with an awesome update. I'm pretty sure this is notabug.
Comment by Maxim (pax) - Saturday, 30 May 2009, 11:23 GMT
I have installed awesome 3.1 on my archlinux machine and the bug was not reproduced. Howewer, after upgrade to awesome 3.2 the bug appeared.
Also the bug is reproducible on my gentoo machine with awesome 3.2.

Is the bug still reproducible in awesome 3.3 ?
Comment by Viacheslav Chumushuk (voice) - Thursday, 15 October 2009, 13:08 GMT
I also have this bug :(
Comment by Nikolaj Sjujskij (krigstask) - Wednesday, 23 December 2009, 21:59 GMT
Seems to work with 3.4

Had to use kxkb before (-:E
Comment by Nikolaj Sjujskij (krigstask) - Thursday, 24 December 2009, 08:41 GMT
I hurried to write previous comment )-:E
xxkb is still unusable and switches layouts unpredictably.
Comment by Igor Rudchenko (igor1st) - Sunday, 03 January 2010, 10:24 GMT
XXkb.controls.add_when_change: yes
XXkb.controls.focusout: yes

xxkb works with this. Not perfectly, but better than non-working at all.
Comment by Nikolaj Sjujskij (krigstask) - Saturday, 09 January 2010, 23:58 GMT
Igor, please explain. What do you mean? What does work and what does not?
Comment by Igor Rudchenko (igor1st) - Sunday, 10 January 2010, 18:57 GMT
This bug is about non-working xxkb after 3.2 version of awesome. And this is true with default xxkb settings, which are 'XXkb.controls.add_when_start' or/and 'XXkb.controls.add_when_create'. I suggest to use xxkb with options 'XXkb.controls.add_when_change' and 'XXkb.controls.focusout' - with them xxkb starts to remember keyboard state for windows, but not perfectly, making mistakes sometimes. At present this is only method of using xxkb with such WM's as awesome/xmonad.
Comment by Nikolaj Sjujskij (krigstask) - Friday, 05 February 2010, 13:48 GMT
> This bug is about non-working xxkb after 3.2 version of awesome
That I did understand (-;E
Asking what does and what does not work, I referred to your then-last comment (#1709). Thanks for explanation (-:E

Comment by Nikolaj Sjujskij (krigstask) - Wednesday, 15 December 2010, 10:10 GMT
For those who tries to make xxkb work with awesome, I've got alternative solution: