You are not logged in.
I work in Arch Linux 64 bit with both English and Hebrew keyboard layouts available, using Alt+Shift to change between them.
I recently noticed that when I work in Texmaker, which is a Qt5 application, when I try to switch the language it will do it, but the Texmaker will ignore the Shift, and just treat the Alt as if I'm going to choose a top menu shortcut next.
Texmaker has a Windows version as well, which I use sometimes, and that's not happening there. But at the same time, in my Firefox, and other text editing software which are all Gtk based, this doesn't happen.
So I decided to ask the developer of Texmaker if something was changed recently, and the answer was negative. Then I decided to install some other Qt5 application which has a top menu, and text input, and much to my dismay the same behavior repeated itself, showing that this is indeed a Qt5 issue.
Is there any way to correct this? I can't say exactly when this happened (I didn't have to type Hebrew into Texmaker for quite some time until now), so it's hard to pinpoint the fault on some particular update or another.
I should perhaps add that I'm using Openbox with SLiM, and have only a few KDE packages installed.
Offline
I just tried to install Kate (with kactivities4), but much to my surprise, this behavior does not occur there.
Is there any way to correct this?
Offline
I did some more digging.
TexStudio, the Texmaker fork, which uses Qt4, has no problem. Which means that this is related to a package accessed by Qt5 applications. The only package that has any signs of keyboard related issues is libxkbcommon-x11 (0.5.0-1 installed from the stable repository).
I did notice that this is a little bit of a latency issue as well. If I hold the ALT key for an additional second, there are no problems at all. But of course that this is not a solution, since holding the ALT key for longer every time I change layouts (which might occur several times in a single line) severely breaks the flow of my typing.
Does this information make the problem easier to pinpoint and correct?
Offline
Okay, I noticed there was a new version out. I took the liberty of preparing the PKGBUILD to compile against Qt4, rather than Qt5 (and I have a newer version!)
Now the problems are gone. So this is definitely a problem with Qt5. Anyone has any idea what I could do about it? Until then, I'll keep recompiling manually against Qt4. Sort of a solution, I suppose.
Offline