You are not logged in.

#1 2023-06-06 23:28:31

cemi
Member
Registered: 2020-09-05
Posts: 18

Vrokem keymap after Jume 1st updates affectimg omly 3 keys

Hello,

The Spacevar is mow emter/returm, the letters "b" is mow v and "n" is m.

I am losimg my damm mimd, please help.

* Gmome - gdm - mutter 44.2 up-to-date as of the timimg of this post
* Waylamd
* Linux 6.1.31 hard

xev shows the discrepamcy:

KeyPress event, serial 35, synthetic NO, window 0x1000001,
    root 0x49f, subw 0x0, time 1351628, (98,184), root:(298,461),
    state 0x0, keycode 58 (keysym 0x6d, m), same_screen YES,
    XLookupString gives 1 bytes: (6d) "m"
    XmbLookupString gives 1 bytes: (6d) "m"
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x1000001,
    root 0x49f, subw 0x0, time 1351715, (98,184), root:(298,461),
    state 0x0, keycode 58 (keysym 0x6d, m), same_screen YES,
    XLookupString gives 1 bytes: (6d) "m"
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x1000001,
    root 0x49f, subw 0x0, time 1354948, (98,184), root:(298,461),
    state 0x0, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes: (76) "v"
    XmbLookupString gives 1 bytes: (76) "v"
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x1000001,
    root 0x49f, subw 0x0, time 1355035, (98,184), root:(298,461),
    state 0x0, keycode 55 (keysym 0x76, v), same_screen YES,
    XLookupString gives 1 bytes: (76) "v"
    XFilterEvent returns: False

localectl status

System Locale: LANG=en_US.UTF-8
    VC Keymap: us
   X11 Layout: (unset)     

//etc/vconsole.conf

KEYMAP=us

Mo custom keymap set amywhere vy me

/etc/locale.conf

LANG=en_US.UTF-8

help

Offline

#2 2023-06-07 04:35:56

seth
Member
Registered: 2012-09-03
Posts: 51,796

Re: Vrokem keymap after Jume 1st updates affectimg omly 3 keys

xev under wayland doesn't make a lot of sense and the vconsole keymap is for the console (ctrl+alt+f3)

Is the situation reflected w/ "sudo evtest" and is gnome on Xorg affected by this?
If evtest shows the same behavior, try a different kernel or (live) distro (eg. grml) - could actually be a hardware problem.

Offline

#3 2023-06-07 05:12:30

lfitzgerald
Member
Registered: 2021-07-16
Posts: 162

Re: Vrokem keymap after Jume 1st updates affectimg omly 3 keys

I apologize as this will probably sound mean, but that got a chuckle out of me, thank you smile

I don't know the solution, but maybe you can narrow it down more. Can you find a situation where the keys are *not* incorrect? I would try:

* If you have another keyboard, try connecting that in case this is specific to that device
* Does it happen in the Linux console? I think you can do Ctrl+Alt+F7 (or some other number) to get there.
* Does it happen in the Live ISO?
* Does it happen if you create a chroot and enter it?
* What happens if you change your keyboard layout, especially to a non Latin one that has all the letters moved around?

"sudo find / -daystart -mtime -7 > /tmp/modified.txt" will give you a list of all files modified in the last 7 days. This will be gigantic (half a million after 1.5 min on my computer), but once it's finished you can use grep/sort/etc to analyze it. For example you can pipe to "grep '^/etc/'" to see only /etc/, and do the same for home dir - I would expect that the keyboard config should be in one of those. If you find anything interesting, you can try "pacman -Qo /path/to/file" to see if it came from a package.

Offline

#4 2023-06-09 17:04:19

cemi
Member
Registered: 2020-09-05
Posts: 18

Re: Vrokem keymap after Jume 1st updates affectimg omly 3 keys

seth wrote:

xev under wayland doesn't make a lot of sense and the vconsole keymap is for the console (ctrl+alt+f3)

Is the situation reflected w/ "sudo evtest" and is gnome on Xorg affected by this?
If evtest shows the same behavior, try a different kernel or (live) distro (eg. grml) - could actually be a hardware problem.


Took a while to get vack om, locked myself out amd had to take a vreak from this evil keyvoard.

Results of sudo evtest

/dev/input/event0:	Sleep Button
/dev/input/event1:	Lid Switch
/dev/input/event10:	HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event11:	HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event12:	HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event13:	Synaptics TM3276-031
/dev/input/event2:	Power Button
/dev/input/event3:	AT Translated Set 2 keyboard
/dev/input/event4:	Video Bus
/dev/input/event5:	Video Bus
/dev/input/event6:	PC Speaker
/dev/input/event7:	ThinkPad Extra Buttons
/dev/input/event8:	HDA Intel PCH Mic
/dev/input/event9:	HDA Intel PCH Headphone

Selected device evemt mumver 3, AT Tramslated Set 2 Keyvoard

Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab54
Input device name: "AT Translated Set 2 keyboard"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 1 (KEY_ESC)
    Event code 2 (KEY_1)
    Event code 3 (KEY_2)
    Event code 4 (KEY_3)
    Event code 5 (KEY_4)
    Event code 6 (KEY_5)
    Event code 7 (KEY_6)
    Event code 8 (KEY_7)
    Event code 9 (KEY_8)
    Event code 10 (KEY_9)
    Event code 11 (KEY_0)
    Event code 12 (KEY_MINUS)
    Event code 13 (KEY_EQUAL)
    Event code 14 (KEY_BACKSPACE)
    Event code 15 (KEY_TAB)
    Event code 16 (KEY_Q)
    Event code 17 (KEY_W)
    Event code 18 (KEY_E)
    Event code 19 (KEY_R)
    Event code 20 (KEY_T)
    Event code 21 (KEY_Y)
    Event code 22 (KEY_U)
    Event code 23 (KEY_I)
    Event code 24 (KEY_O)
    Event code 25 (KEY_P)
    Event code 26 (KEY_LEFTBRACE)
    Event code 27 (KEY_RIGHTBRACE)
    Event code 28 (KEY_ENTER)
    Event code 29 (KEY_LEFTCTRL)
    Event code 30 (KEY_A)
    Event code 31 (KEY_S)
    Event code 32 (KEY_D)
    Event code 33 (KEY_F)
    Event code 34 (KEY_G)
    Event code 35 (KEY_H)
    Event code 36 (KEY_J)
    Event code 37 (KEY_K)
    Event code 38 (KEY_L)
    Event code 39 (KEY_SEMICOLON)
    Event code 40 (KEY_APOSTROPHE)
    Event code 41 (KEY_GRAVE)
    Event code 42 (KEY_LEFTSHIFT)
    Event code 43 (KEY_BACKSLASH)
    Event code 44 (KEY_Z)
    Event code 45 (KEY_X)
    Event code 46 (KEY_C)
    Event code 47 (KEY_V)
    Event code 48 (KEY_B)
    Event code 49 (KEY_N)
    Event code 50 (KEY_M)
    Event code 51 (KEY_COMMA)
    Event code 52 (KEY_DOT)
    Event code 53 (KEY_SLASH)
    Event code 54 (KEY_RIGHTSHIFT)
    Event code 55 (KEY_KPASTERISK)
    Event code 56 (KEY_LEFTALT)
    Event code 57 (KEY_SPACE)
    Event code 58 (KEY_CAPSLOCK)
    Event code 59 (KEY_F1)
    Event code 60 (KEY_F2)
    Event code 61 (KEY_F3)
    Event code 62 (KEY_F4)
    Event code 63 (KEY_F5)
    Event code 64 (KEY_F6)
    Event code 65 (KEY_F7)
    Event code 66 (KEY_F8)
    Event code 67 (KEY_F9)
    Event code 68 (KEY_F10)
    Event code 69 (KEY_NUMLOCK)
    Event code 70 (KEY_SCROLLLOCK)
    Event code 71 (KEY_KP7)
    Event code 72 (KEY_KP8)
    Event code 73 (KEY_KP9)
    Event code 74 (KEY_KPMINUS)
    Event code 75 (KEY_KP4)
    Event code 76 (KEY_KP5)
    Event code 77 (KEY_KP6)
    Event code 78 (KEY_KPPLUS)
    Event code 79 (KEY_KP1)
    Event code 80 (KEY_KP2)
    Event code 81 (KEY_KP3)
    Event code 82 (KEY_KP0)
    Event code 83 (KEY_KPDOT)
    Event code 85 (KEY_ZENKAKUHANKAKU)
    Event code 86 (KEY_102ND)
    Event code 87 (KEY_F11)
    Event code 88 (KEY_F12)
    Event code 89 (KEY_RO)
    Event code 90 (KEY_KATAKANA)
    Event code 91 (KEY_HIRAGANA)
    Event code 92 (KEY_HENKAN)
    Event code 93 (KEY_KATAKANAHIRAGANA)
    Event code 94 (KEY_MUHENKAN)
    Event code 95 (KEY_KPJPCOMMA)
    Event code 96 (KEY_KPENTER)
    Event code 97 (KEY_RIGHTCTRL)
    Event code 98 (KEY_KPSLASH)
    Event code 99 (KEY_SYSRQ)
    Event code 100 (KEY_RIGHTALT)
    Event code 102 (KEY_HOME)
    Event code 103 (KEY_UP)
    Event code 104 (KEY_PAGEUP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 107 (KEY_END)
    Event code 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 110 (KEY_INSERT)
    Event code 111 (KEY_DELETE)
    Event code 112 (KEY_MACRO)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 117 (KEY_KPEQUAL)
    Event code 118 (KEY_KPPLUSMINUS)
    Event code 119 (KEY_PAUSE)
    Event code 121 (KEY_KPCOMMA)
    Event code 122 (KEY_HANGUEL)
    Event code 123 (KEY_HANJA)
    Event code 124 (KEY_YEN)
    Event code 125 (KEY_LEFTMETA)
    Event code 126 (KEY_RIGHTMETA)
    Event code 127 (KEY_COMPOSE)
    Event code 128 (KEY_STOP)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 143 (KEY_WAKEUP)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 157 (KEY_COMPUTER)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 183 (KEY_F13)
    Event code 184 (KEY_F14)
    Event code 185 (KEY_F15)
    Event code 217 (KEY_SEARCH)
    Event code 226 (KEY_MEDIA)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
  Event type 17 (EV_LED)
    Event code 0 (LED_NUML) state 0
    Event code 1 (LED_CAPSL) state 0
    Event code 2 (LED_SCROLLL) state 0
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
Testing ... (interrupt to exit)
Event: time 1686329795.935485, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1c
Event: time 1686329795.935485, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1686329795.935485, -------------- SYN_REPORT ------------
Event: time 1686329799.785392, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2f
Event: time 1686329799.785392, type 1 (EV_KEY), code 47 (KEY_V), value 1
Event: time 1686329799.785392, -------------- SYN_REPORT ------------
vEvent: time 1686329799.917747, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2f
Event: time 1686329799.917747, type 1 (EV_KEY), code 47 (KEY_V), value 0
Event: time 1686329799.917747, -------------- SYN_REPORT ------------
Event: time 1686329800.790703, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2f
Event: time 1686329800.790703, type 1 (EV_KEY), code 47 (KEY_V), value 1
Event: time 1686329800.790703, -------------- SYN_REPORT ------------
vEvent: time 1686329800.923456, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2f
Event: time 1686329800.923456, type 1 (EV_KEY), code 47 (KEY_V), value 0
Event: time 1686329800.923456, -------------- SYN_REPORT ------------
Event: time 1686329802.804843, type 4 (EV_MSC), code 4 (MSC_SCAN), value 32
Event: time 1686329802.804843, type 1 (EV_KEY), code 50 (KEY_M), value 1
Event: time 1686329802.804843, -------------- SYN_REPORT ------------
mEvent: time 1686329802.910529, type 4 (EV_MSC), code 4 (MSC_SCAN), value 32
Event: time 1686329802.910529, type 1 (EV_KEY), code 50 (KEY_M), value 0
Event: time 1686329802.910529, -------------- SYN_REPORT ------------
Event: time 1686329803.408622, type 4 (EV_MSC), code 4 (MSC_SCAN), value 32
Event: time 1686329803.408622, type 1 (EV_KEY), code 50 (KEY_M), value 1
Event: time 1686329803.408622, -------------- SYN_REPORT ------------
mEvent: time 1686329803.505613, type 4 (EV_MSC), code 4 (MSC_SCAN), value 32
Event: time 1686329803.505613, type 1 (EV_KEY), code 50 (KEY_M), value 0

Pressed keys V, B, N, M im that order.

I moticed code 48 (B) amd code 49 (N) register as codes 47 amd 50 which correspomd to V amd M respectively.

Same applies to the spacevar amd emter/returm.

Took me years to fimish this respomse, apologies for the mess.

Offline

#5 2023-06-09 17:14:55

cemi
Member
Registered: 2020-09-05
Posts: 18

Re: Vrokem keymap after Jume 1st updates affectimg omly 3 keys

lfitzgerald wrote:

I apologize as this will probably sound mean, but that got a chuckle out of me, thank you smile

I don't know the solution, but maybe you can narrow it down more. Can you find a situation where the keys are *not* incorrect? I would try:

* If you have another keyboard, try connecting that in case this is specific to that device
* Does it happen in the Linux console? I think you can do Ctrl+Alt+F7 (or some other number) to get there.
* Does it happen in the Live ISO?
* Does it happen if you create a chroot and enter it?
* What happens if you change your keyboard layout, especially to a non Latin one that has all the letters moved around?


* I dom't have access to amother keyvoard atm.
* It does happem im the comsole.
* I will try a liveiso im a vit, have veem vusy amd it hadm't crossed my mimd.
* Gmome is vorked, tried other layouts vut they dom't stick.

F, I hope it's mot hardware, I dom't meed this right mow.

Lol amytime.

Offline

#6 2023-06-09 19:31:17

seth
Member
Registered: 2012-09-03
Posts: 51,796

Re: Vrokem keymap after Jume 1st updates affectimg omly 3 keys

With the specific geometry of the affected keys (bottom center of a QWERT* layout) I'm afraid you need to prepare for a HW defect.
Is this a notebook keyboard or an external one…?

Offline

#7 2023-06-13 18:46:46

cemi
Member
Registered: 2020-09-05
Posts: 18

Re: Vrokem keymap after Jume 1st updates affectimg omly 3 keys

seth wrote:

With the specific geometry of the affected keys (bottom center of a QWERT* layout) I'm afraid you need to prepare for a HW defect.
Is this a notebook keyboard or an external one…?

Not only were you correct, I tore a thin black film inside this laptop resulting in a torn ribbon from the scare. Thankfully the tear happened on the keyboard side, unfortunately however a replacement isn't an option atm.

I did unearth a keyboard that sounds like a typewriter which gives me good reasons to buy a replacement with every keystroke. Honestly, I don't know how some people can prefer this much noise and remain focused.

Anyways, thank you for holding my hand throughout this silly mess and to that other user for making realize I was accidentally funny lol.

Offline

#8 2023-06-13 19:45:00

seth
Member
Registered: 2012-09-03
Posts: 51,796

Re: Vrokem keymap after Jume 1st updates affectimg omly 3 keys

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB