You are not logged in.
Pages: 1
Hello,
I am having a problem with the language settings, I have two languages installed(English and Hebrew) and right now only the English is working fine.
When I try to write something in Hebrew I will get some characters in Hebrew and some in English seamlessly at random, the key won't always give an output in the same language(for example: I can press 'e' a couple of times and in some of the times it will give me me some sort of 9 length permutation of the letter in Hebrew and English: 'eeeקקקקקקקeeeקee' or 'eeeeeeeeeeeeקe' )
I'm using Gnome on Xorg(Wayland doesn't seem to work, but that is a problem for another time).
I really have no idea what to look for and where.
Last edited by logan123 (2017-05-27 18:59:40)
Offline
Sounds like it might be your keyboard malfunctioning. If you can, try another keyboard and see if that fixes it. If not, you'll have to wait for someone else because I know next to nothing about switching languages.
Offline
My hebrew is a bit hazy (it's been some thousand years ... ;-) - but "ק" is more like "k", isn't?
Is is the symbol on the "e" key (ie. do you get this letter when setting input to hebrew and press the "e" key)?
Online
I tried another keyboard, didn't work.
Is is the symbol on the "e" key (ie. do you get this letter when setting input to hebrew and press the "e" key)?
Yes it is the letter I am suppose to get when I set the input to hebrew
btw
but "ק" is more like "k", isn't?
Yep
Offline
Ok, how do you switch input languages? Do you use an input tool (ibus, scim, etc) or a shortcut or a systray icon, ....?
setxkbmap -print -queryAlso lookup your xorg log to check whether you're using libinput or evdev as keyboard input driver (and the implication is: try the other one ;-)
Online
I'm using libinput, I tried switching to evdev and it didn't change anything.
I have no idea how I can find out which input tool I'm using but since I'm using Gnome doesn't that mean that its some sort of integrate ibus?
$ grep -e "Using input" /var/log/Xorg.0.log
[ 6.349] (II) Using input driver 'libinput' for 'Power Button'
[ 6.370] (II) Using input driver 'libinput' for 'Power Button'
[ 6.372] (II) Using input driver 'libinput' for 'Microsoft Natural® Ergonomic Keyboard 4000'
[ 6.374] (II) Using input driver 'libinput' for 'Microsoft Natural® Ergonomic Keyboard 4000'
[ 6.375] (II) Using input driver 'libinput' for 'Mad Catz Mad Catz RAT6'
[ 6.431] (II) Using input driver 'libinput' for 'Mad Catz Mad Catz RAT6'
[ 6.433] (II) Using input driver 'libinput' for 'Mad Catz Mad Catz RAT6'
[ 6.437] (II) Using input driver 'libinput' for 'Microsoft Natural® Ergonomic Keyboard 4000'
[ 6.438] (II) Using input driver 'libinput' for 'Mad Catz Mad Catz RAT6'
$ setxkbmap -print -query
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+il:2+us:3+inet(evdev)+group(alt_shift_toggle)" };
xkb_geometry { include "pc(pc105)" };
};
rules: evdev
model: pc105
layout: us,il,us
variant: ,
options: grp:alt_shift_togglewhy does it say evdev if I'm using libinput?
Offline
"rules", not "driver" - the "Using input driver" line changed after switchgin to evdev?
Interestingly, you've 3 layouts: us - il - us. Is that by intent?
You switch layouts by pressing alt+shift, but your rodant is more interesting. I bet it shows up as keyboard as well. Does the problem occur when replacing the 'Mad Catz Mad Catz RAT6' mouse with a more basic 3-button mouse?
Online
"rules", not "driver" - the "Using input driver" line changed after switchgin to evdev?
Yes.
Interestingly, you've 3 layouts: us - il - us. Is that by intent?
No but I tried to change it with
setxkbmap -layout us,ildidn't change anything
You switch layouts by pressing alt+shift, but your rodant is more interesting. I bet it shows up as keyboard as well. Does the problem occur when replacing the 'Mad Catz Mad Catz RAT6' mouse with a more basic 3-button mouse?
I have been using this mouse for a couple of months now, but yes it still happens even without it.
Offline
Ok. Can you reproduce this in any client? xterm? (not! terminator)
If so, run "xev -event keyboard | tee xev.log" and press the e key until a ק is produces. Paste the log.
Online
Outer window is 0x2800001, inner window is 0x2800002
KeymapNotify event, serial 24, synthetic NO, window 0x0,
keys: 4294967208 0 0 0 16 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 25, synthetic NO, window 0x2800001,
root 0x1d8, subw 0x0, time 20765881, (290,308), root:(340,422),
state 0x10, keycode 36 (keysym 0xff0d, Return), same_screen YES,
XLookupString gives 1 bytes: (0d) "
"
XFilterEvent returns: False
KeyPress event, serial 28, synthetic NO, window 0x2800001,
root 0x1d8, subw 0x0, time 20767121, (291,308), root:(341,422),
state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
XLookupString gives 1 bytes: (65) "e"
XmbLookupString gives 1 bytes: (65) "e"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x2800001,
root 0x1d8, subw 0x0, time 20767241, (291,308), root:(341,422),
state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
XLookupString gives 1 bytes: (65) "e"
XFilterEvent returns: False
KeyPress event, serial 28, synthetic NO, window 0x2800001,
root 0x1d8, subw 0x0, time 20768761, (292,309), root:(342,423),
state 0x2010, keycode 26 (keysym 0xcf7, hebrew_qoph), same_screen YES,
XLookupString gives 2 bytes: (d7 a7) "ק"
XmbLookupString gives 2 bytes: (d7 a7) "ק"
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0x2800001,
root 0x1d8, subw 0x0, time 20768865, (292,309), root:(342,423),
state 0x2010, keycode 26 (keysym 0xcf7, hebrew_qoph), same_screen YES,
XLookupString gives 2 bytes: (d7 a7) "ק"
XFilterEvent returns: FalseOffline
That's all? 0x2010 means mode switch (0x2000) + numlock (0x10), so the mode_switch is considered pressed, thus the other language.
Did you modmap mode_switch to some physical key?
xmodmap -pk | grep Mode_switchOnline
203 0xff7e (Mode_switch) 0x0000 (NoSymbol) 0xff7e (Mode_switch) 0x0000 (NoSymbol) 0xff7e (Mode_switch)Offline
You cant close the topic and mark it solved, it all happen because of a program named Fcitx, no idea where it came from but closing it fixed the problem.
thank you for all the help.
Offline
Finally, when a solution is found, mark your thread as solved by editing the first post and prepending the tag [SOLVED] to the title in the "Subject" field.
Note that you should avoid using [CLOSED], which is instead used by the system to mark a thread which is no longer accessible for new posts.
Offline
Do you use an input tool (ibus, scim, etc)
"etc" ;-)
pacman -Qi fcitxThis should tell you why it was installed (though it's hardly a dep for anything)
Since the package adds a desktop service into xdg/autostart, it's started with xdg compliant desktop sessions.
Online
Finally, when a solution is found, mark your thread as solved by editing the first post and prepending the tag [SOLVED] to the title in the "Subject" field.
Note that you should avoid using [CLOSED], which is instead used by the system to mark a thread which is no longer accessible for new posts.
Good to know, will do.
"etc" ;-)
Well I had no idea how to find it ![]()
anyway thank you for everything.
Offline
Pages: 1