Open 0hCome0n opened 1 month ago
If this isn't the right place to report this let me know, I'm very new to this stuff.
Also, if there are any other tests I should run, please let me know. I'd like to help figure this out as much as I can.
Does the same happen with other distros/OSes or is it just Mint cinnamon?
Okay I just tested with Windows 10 and a USB version of Ubuntu 24.04 LTS. The bug was present in Ubuntu but not in Windows. If there's any other Operating systems worth testing let me know. Is there a more "base" level OS I should be looking at? I should probably try to report the bug at the lowest level possible, yeah?
Please also report this bug to the Ubuntu team.
Will do.
I just tried it with Arch but I couldn't figure out how to get past the initial setup screen. The bug doesn't exist on that initial terminal screen in set-up. That prompted me to try typing on that temporary CLI login that shows up when starting Mint from a full power off and the bug does not exist there.
So recap so far:
Mint - Yes Mint Temp CLI Login - No Ubuntu - Yes Arch - Maybe not? Windows - No
Most likely a kernel issue. What's the make and model of the keyboard?
Which kernel (uname -r
)?
Try launching the Driver Manager (in the System Settings).
Are you sure this isn't a hardware issue? Can you try plugging in another keyboard? I used to have a Logitech keyboard that had an issue similar to this and it didn't happen all the time.
Kernel: 5.15.0-107-generic
Keyboard: 01AX120 (the integrated keyboard on the laptop)
I don't believe this is a hardware issue because the button behaves as expected in windows and in the Arch install command line interface. Plus the evtest output doesn't spit out the following over and over like it does if you hold it down:
Event: time 1715974930.271262, type 4 (EV_MSC), code 4 (MSC_SCAN), value 0e
Event: time 1715974930.271262, type 1 (EV_KEY), code 14 (KEY_BACKSPACE), value 0
Event: time 1715974930.271262, -------------- SYN_REPORT ------------
I checked Driver Manager but for some reason I'm only seeing the GPU driver options and nothing else. However, I figured out how to get the terminal to spit out a list of all the drivers. The problem being I don't know which one is the one I'm supposed to be interested in, so I don't know which one to ask the terminal to give me details about.
Here's the list, which ones should I get more info on?
Module Size Used by
rfcomm 81920 16
ccm 20480 6
cmac 16384 3
algif_hash 16384 1
algif_skcipher 16384 1
af_alg 32768 6 algif_hash,algif_skcipher
bnep 28672 2
ip6t_REJECT 16384 1
nf_reject_ipv6 20480 1 ip6t_REJECT
xt_hl 16384 22
ip6_tables 32768 52
ip6t_rt 20480 3
ipt_REJECT 16384 1
nf_reject_ipv4 16384 1 ipt_REJECT
xt_LOG 20480 10
nf_log_syslog 20480 10
nft_limit 16384 13
xt_limit 16384 0
xt_addrtype 16384 4
xt_tcpudp 20480 36
xt_conntrack 16384 16
nf_conntrack 172032 1 xt_conntrack
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
nft_compat 20480 153
nft_counter 16384 188
nf_tables 266240 443 nft_compat,nft_counter,nft_limit
nfnetlink 20480 2 nft_compat,nf_tables
binfmt_misc 24576 1
zfs 4112384 0
zunicode 348160 1 zfs
zzstd 491520 1 zfs
zlua 163840 1 zfs
zavl 16384 1 zfs
icp 311296 1 zfs
zcommon 106496 2 zfs,icp
znvpair 98304 2 zfs,zcommon
spl 118784 6 zfs,icp,zzstd,znvpair,zcommon,zavl
snd_soc_skl 172032 0
snd_soc_hdac_hda 24576 1 snd_soc_skl
snd_hda_ext_core 32768 2 snd_soc_hdac_hda,snd_soc_skl
snd_soc_sst_ipc 20480 1 snd_soc_skl
snd_soc_sst_dsp 36864 1 snd_soc_skl
snd_soc_acpi_intel_match 61440 1 snd_soc_skl
snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_soc_skl
snd_soc_core 348160 2 snd_soc_hdac_hda,snd_soc_skl
snd_hda_codec_hdmi 77824 1
snd_compress 24576 1 snd_soc_core
ac97_bus 16384 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_ctl_led 24576 0
snd_hda_codec_conexant 28672 1
intel_rapl_msr 20480 0
intel_rapl_common 40960 1 intel_rapl_msr
intel_tcc_cooling 16384 0
snd_hda_codec_generic 102400 1 snd_hda_codec_conexant
x86_pkg_temp_thermal 20480 0
intel_powerclamp 24576 0
snd_hda_intel 53248 5
uvcvideo 106496 0
coretemp 24576 0
snd_intel_dspcfg 28672 2 snd_hda_intel,snd_soc_skl
snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg
btusb 61440 0
snd_hda_codec 163840 5 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_soc_hdac_hda
btrtl 24576 1 btusb
ath10k_pci 49152 0
snd_hda_core 110592 8 snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_hdac_hda,snd_soc_skl
ath10k_core 602112 1 ath10k_pci
mei_hdcp 24576 0
kvm_intel 372736 0
btbcm 24576 1 btusb
videobuf2_vmalloc 20480 1 uvcvideo
videobuf2_memops 20480 1 videobuf2_vmalloc
snd_hwdep 16384 1 snd_hda_codec
kvm 1032192 1 kvm_intel
videobuf2_v4l2 32768 1 uvcvideo
ath 36864 1 ath10k_core
videobuf2_common 77824 4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
mac80211 1249280 1 ath10k_core
snd_pcm 143360 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
thinkpad_acpi 131072 0
btintel 40960 1 btusb
videodev 258048 3 videobuf2_v4l2,uvcvideo,videobuf2_common
nvram 16384 1 thinkpad_acpi
ledtrig_audio 16384 3 snd_ctl_led,snd_hda_codec_generic,thinkpad_acpi
nls_iso8859_1 16384 1
snd_seq_midi 20480 0
cfg80211 974848 3 ath,mac80211,ath10k_core
snd_seq_midi_event 16384 1 snd_seq_midi
rapl 20480 0
snd_rawmidi 49152 1 snd_seq_midi
bluetooth 704512 43 btrtl,btintel,btbcm,bnep,btusb,rfcomm
snd_seq 77824 2 snd_seq_midi,snd_seq_midi_event
mc 65536 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
mei_me 40960 1
intel_cstate 20480 0
libarc4 16384 1 mac80211
joydev 32768 0
input_leds 16384 0
ecdh_generic 16384 2 bluetooth
ecc 36864 1 ecdh_generic
snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi
snd_timer 40960 2 snd_seq,snd_pcm
mei 135168 3 mei_hdcp,mei_me
snd 106496 24 snd_ctl_led,snd_hda_codec_generic,snd_seq,snd_hda_codec_conexant,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_timer,snd_compress,thinkpad_acpi,snd_soc_core,snd_pcm,snd_rawmidi
serio_raw 20480 0
ee1004 20480 0
soundcore 16384 2 snd_ctl_led,snd
intel_xhci_usb_role_switch 16384 0
platform_profile 16384 1 thinkpad_acpi
intel_pch_thermal 20480 0
nvidia_uvm 1511424 0
mac_hid 16384 0
think_lmi 28672 0
wmi_bmof 16384 0
firmware_attributes_class 16384 1 think_lmi
sch_fq_codel 20480 2
msr 16384 0
parport_pc 49152 0
ppdev 24576 0
lp 28672 0
parport 69632 3 parport_pc,lp,ppdev
efi_pstore 16384 0
ip_tables 32768 8
x_tables 53248 12 xt_conntrack,nft_compat,xt_LOG,xt_tcpudp,xt_addrtype,ip6t_rt,ip6_tables,ipt_REJECT,ip_tables,xt_limit,xt_hl,ip6t_REJECT
autofs4 49152 2
btrfs 1564672 0
blake2b_generic 20480 0
xor 24576 1 btrfs
zstd_compress 229376 1 btrfs
raid6_pq 122880 1 btrfs
libcrc32c 16384 3 nf_conntrack,btrfs,nf_tables
dm_mirror 24576 0
dm_region_hash 24576 1 dm_mirror
dm_log 20480 2 dm_region_hash,dm_mirror
nvidia_drm 77824 2
nvidia_modeset 1306624 2 nvidia_drm
nvidia 56717312 100 nvidia_uvm,nvidia_modeset
i915 3117056 36
i2c_algo_bit 16384 1 i915
ttm 86016 1 i915
crct10dif_pclmul 16384 1
crc32_pclmul 16384 0
ghash_clmulni_intel 16384 0
sha256_ssse3 32768 0
drm_kms_helper 311296 2 nvidia_drm,i915
r8169 102400 0
syscopyarea 16384 1 drm_kms_helper
sysfillrect 20480 1 drm_kms_helper
i2c_i801 36864 0
sysimgblt 16384 1 drm_kms_helper
sha1_ssse3 32768 0
fb_sys_fops 16384 1 drm_kms_helper
aesni_intel 376832 8
crypto_simd 16384 1 aesni_intel
psmouse 176128 0
cryptd 24576 3 crypto_simd,ghash_clmulni_intel
cec 61440 2 drm_kms_helper,i915
sdhci_pci 69632 0
realtek 32768 1
i2c_smbus 20480 1 i2c_i801
rc_core 65536 1 cec
nvme 49152 1
drm 622592 21 drm_kms_helper,nvidia,nvidia_drm,i915,ttm
cqhci 36864 1 sdhci_pci
sdhci 81920 1 sdhci_pci
ahci 49152 1
xhci_pci 24576 0
nvme_core 135168 2 nvme
libahci 49152 1 ahci
xhci_pci_renesas 20480 1 xhci_pci
wmi 32768 2 wmi_bmof,think_lmi
video 65536 2 thinkpad_acpi,i915
Try using the Linux kernel 6.5. Open mintupdate; then select Linux kernels in the View menu and install version 6.5. Reboot your computer. Update your packages then reboot again.
Okay, I'm now on kernel: 6.5.0-35-generic
The bug persists with the same behavior and the same output from evtest when I test the keyboard.
From what I've read, the evtest output is telling us this is a kernel issue? Who is in charge of the kernel? I'm perfectly happy to work with them to get to the bottom of this.
The kernel change solved some of my hardware problems.
In cinnamon you could try:
sudo dpkg-reconfigure keyboard-configuration
and set keyboard to Do not configure keyboard; keep kernel keymap
?
Given the following Terminal Command
sudo dpkg-reconfigure keyboard-configuration
The Default keyboard setting was
Generic 105-key PC
and the new settings were
Do not configure keyboard; keep kernel keymap
English (US)
English (US) - English (Dvorak)
No AltGr key
No compose key
"No" to ctrl + alt + backspace shortcut
Following a system reboot after letting the computer finish making the changes, the bug remains,
Even if we don't figure this out I'm grateful for your help.
Also, there was not a specific keyboard layout for the this laptop in the presets (Lenovo Thinkpad E570)
Okay it looks like Lenovo uses some kind of special layer for the number pad when working with windows.
https://unix.stackexchange.com/questions/494698/thinkpad-second-sticky-backspace-key
Although that still doesn't fully explain why it works properly before the kernel loads. I don't really know when the kernel loads or even what it takes over from, I'm just guessing that something else is in control for those CLI parts where there's no bug.
Distribution
Linux Mint 21.3 Virginia
Package version
6.0.4
Graphics hardware in use
NVIDIA GM107M [GeForce GTX 950M]
Frequency
Always
Bug description
A single press on the numberpad backspace key causes the computer to think the key is held down. The continuous backspace only stops when another key is pressed. From playing around with a CLI program called evtest, it seems the computer sets the key value to 1 on press but doesn't set it to 0 on release. For other keys, a return to 0 is the normal behavior. Evtest will repeatedly report a value of 2 if a key is pressed and held, and it does this correctly with the numberpad backspace. However, a single press on the numberpad backspace and then a single press with the regular backspace shows a value of 2 for the second key even though the first was not held.
The standard backspace key behaves as normal.
Steps to reproduce
Open a text file and populate it with text
Press the numberpad backspace
watch the cursor eat the text without your help
press any other key to stop the madness
Expected behavior
Should behave the same as the ordinary backspace
Additional information
Output from evtest on the following button combination:
Down Backspace Numberpad Backspace Numberpad Backspace Backspace Backspace Numberpad Backspace Down Numberpad Backspace Down Backspace Down Backspace
----------System Report----------