Mouse's right click gets locked and is unresponsive

[tut]

I just installed MX-23.3_x64 on my laptop a few days ago. However, it keeps locking up the right click on my wired mouse. I then realized clicking on the RMB on my touchpad unlocks the right click ability. Any way to diagnose why this keeps happening?

Code: Select all

[CODE]System:
  Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-21-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.3_x64 Libretto May 19  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: Hewlett-Packard product: HP EliteBook 820 G2 v: A3009D510203
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Hewlett-Packard model: 225A v: KBC Version 96.5B serial: <superuser required>
    UEFI: Hewlett-Packard v: M71 Ver. 01.31 date: 02/24/2020
Battery:
  ID-1: BAT0 charge: 30.3 Wh (93.5%) condition: 32.4/32.4 Wh (100.0%) volts: 12.2 min: 11.1
    model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: not charging
CPU:
  Info: model: Intel Core i5-5300U bits: 64 type: MT MCP arch: Broadwell gen: core 5 level: v3
    note: check built: 2015-18 process: Intel 14nm family: 6 model-id: 0x3D (61) stepping: 4
    microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1550 high: 1580 min/max: 500/2900 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1530 2: 1574 3: 1519 4: 1580 bogomips: 18357
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: Clear CPU buffers; SMT vulnerable
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-8
    process: Intel 14nm built: 2014-15 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:1616 class-ID: 0300
  Device-2: Cheng Uei Precision Industry (Foxlink) HP EliteBook integrated HD Webcam type: USB
    driver: uvcvideo bus-ID: 1-1.7:7 chip-ID: 05c8:0374 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: eDP-1 model: LG Display 0x03ee built: 2012 res: 1366x768 hz: 60 dpi: 125 gamma: 1.2
    size: 277x156mm (10.91x6.14") diag: 318mm (12.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 5500 (BDW GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Broadwell-U Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    bus-ID: 00:03.0 chip-ID: 8086:160c class-ID: 0403
  Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0 class-ID: 0403
  API: ALSA v: k6.1.0-21-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I218-LM vendor: Hewlett-Packard driver: e1000e v: kernel port: 5080
    bus-ID: 00:19.0 chip-ID: 8086:15a2 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-1.4:4
    chip-ID: 8087:0a2a class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: 1000 hci-v: 4.0 rev: 1000
  Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 465.76 GiB used: 12.84 GiB (2.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST500VT000-1DK142 size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: SDC1 scheme: GPT
Partition:
  ID-1: / raw-size: 465.51 GiB size: 457.13 GiB (98.20%) used: 12.84 GiB (2.8%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2457 libs: 1053 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mxlinux.mirror.liquidtelecom.com/packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/vscodium.list
    1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium main
Info:
  Processes: 227 Uptime: 5h 15m wakeups: 2 Memory: 7.63 GiB used: 3.38 GiB (44.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[/code]

[j2mcgreg]

Assuming that you have already tested you mouse with a fresh battery or your computer with another mouse:
The 6.1.xxx kernel is known to be buggy. I think that you should use MXPI to install one of the Liquorix kernels that are available. As a starting point I suggest either the Liquorix 6.5.xxx or 6.6.xxx. After the install is complete, reboot, at the Grub screen select Advanced Options and then select the Liquorix kernel as the boot choice for this session. If the new kernel solves the problem, you can make the switch permanent with Boot Options in MX Tools.

[Charlie Brown]

... at the Grub screen select Advanced Options and then select the Liquorix kernel as the boot choice for this session. If the new kernel solves the problem, you can make the switch permanent with Boot Options in MX Tools. ..

Once installed it'll already become the default (by itself) and you don't need to select that specifically. (As it'll have a higher number than the current one).

[j2mcgreg]

... at the Grub screen select Advanced Options and then select the Liquorix kernel as the boot choice for this session. If the new kernel solves the problem, you can make the switch permanent with Boot Options in MX Tools. ..

Once installed it'll already become the default (by itself) and you don't need to select that specifically. (As it'll have a higher number than the current one).

I do it this way so that newbies also get introduced to Boot Options which they will need if the kernel upgrade doesn't workout and they want to roll back.

[tut]

Assuming that you have already tested you mouse with a fresh battery or your computer with another mouse:

This laptop previously had Windows 10 and the mouse worked fine.

I installed `Liquorix 6.6.12-1 64 bit` and I guess I made it the default by typing `Y` in the installation process (I am a noob, lol). But I will test this for a few days and see if the issue does pop up again (and mark this topic as resolved). Thank you all.

[Charlie Brown]

... typing `Y` in the installation process ...

That was just to confirm the installation :)

[tut]

The issue just popped up again with

Code: Select all

Liquorix 6.6.12-1 64 bit

.

[siamhie]

Have you tried all the available USB ports?

[Charlie Brown]

In case you'd like to turn back to (the good old) Synaptics :

Code: Select all

sudo mv /etc/X11/xorg.conf.d/30-touchpad-libinput.conf{,.old} ; sudo apt update ; sudo apt install xserver-xorg-input-synaptics -y

Reboot (and try).


To revert back to libinput (for whatever reason) :

Code: Select all

sudo mv /etc/X11/xorg.conf.d/30-touchpad-libinput.conf.old /etc/X11/xorg.conf.d/30-touchpad-libinput.conf ; sudo apt remove xserver-xorg-input-synaptics -y

Reboot.

[tut]

Have you tried all the available USB ports?

Yes!

In case you'd like to turn back to (the good old) Synaptics

That didn't help either.

Btw, even now writing this, the issue just popped up a few seconds ago. Just to be clear, this PC was on Windows 10 and the mouse was working. Other than switching to another distro, I don't know how to diagnose this further.