Mouse cursor jumps to left edge of the screen after today's system update

Hi guys,

I just updated the Manjaro install on my Thinkpad L13 Yoga Gen2. Since the update I have the issue that the mouse cursor sporadically (actually quite frequently) jumps to the left screen edge. If I try to move it back to the right, it is sometimes like somebody is fighting me and tries to move it to the left again.

Some further infos:

  • I have deactivated the touchpad and only use the trackpoint
  • I tried to switch to an older kernel (5.15 to be more precise) with no effect
  • update log: Manjaro update log -

Thanks for any ideas!

The problem also appears in the Bios menu. Looks like the linux-firmware update is the problem. But downgrading it to the previous version didn’t solve the issue. So far, the only workaround was to deactivate the trackpoint and activate the touchpad, but I absolutely hate using the touchpad and would love to get my trackpoint back, so yeah…

Is it this one ?
Please provide some info, you are long enough around here.
Does it also happen with a live system (try manjaro, you may also try ubuntu) ?

Yes, exactly!

Well, it happens in the BIOS menu, as I stated in my previous post, so it will for sure happen with a live system as well. I assume that the linux-firmware update messed up something…

…if you don’t have 15 min for investigating, then…

I happen to have a Kubuntu 20.04 flash drive, so I will have a look asap and report back!

Update: Confirmed, it also happens on Kubuntu.

The info about your device is sparse as far as linux is concerned.
There are hacks, but only for other models. You should look in /var/log/messages for psmouse and trackpoint entries, maybe… but all speculation, without system info.
Some links:

I can provide whatever system info is necessary, just let me know what it is. I assume that hardware like CPU, RAM or hard disk space is irrelevant here, that’s why I haven’t provided information about it. Here’s my inxi -F if it helps anyhow:

$ inxi -F
  Host: ThinkpadL13Yoga Kernel: 5.15.65-1-MANJARO arch: x86_64 bits: 64
    Desktop: Xfce v: 4.16.1 Distro: Manjaro Linux
  Type: Convertible System: LENOVO product: 20VLS01500 v: ThinkPad L13 Yoga
    Gen 2 serial: <superuser required>
  Mobo: LENOVO model: 20VLS01500 serial: <superuser required> UEFI: LENOVO
    v: R1FET29W (1.03 ) date: 10/08/2020
  ID-1: BAT0 charge: 33.0 Wh (79.7%) condition: 41.4/46.0 Wh (90.0%)
  Info: quad core model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP
    cache: L2: 5 MiB
  Speed (MHz): avg: 1279 min/max: 400/4200 cores: 1: 1300 2: 1299 3: 1231
    4: 1301 5: 1300 6: 1168 7: 1334 8: 1306
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: Chicony ThinkPad T490 Webcam type: USB driver: uvcvideo
  Device-3: Acer Integrated 5M Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: modesetting
    gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 22.1.7
  Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.15.65-1-MANJARO running: yes
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.57 running: yes
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi
  IF: wlp0s20f3 state: up mac: 2c:db:07:e7:59:78
  Device-2: Intel Ethernet I219-V driver: e1000e
  IF: enp0s31f6 state: down mac: 48:2a:e3:a8:52:2b
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
  Local Storage: total: 476.94 GiB used: 60.87 GiB (12.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L7
    size: 476.94 GiB
  ID-1: / size: 71.04 GiB used: 60.87 GiB (85.7%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 296 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
  System Temperatures: cpu: 17.0 C mobo: N/A
  Fan Speeds (RPM): fan-1: 0
  Processes: 301 Uptime: 4h 23m Memory: 15.3 GiB used: 5.07 GiB (33.1%)
  Shell: Bash inxi: 3.3.21

I grepped the journal for psmouse but the output before and after the update were identical.

  • BIOS Update (Bootable CD)
  • 15 Aug 2022
    …confirm with your serial number, please.

Looks like your machine is listed in

Is fwupd or gnome-firmware installed ? If not, install one (up to you) and let it search for bios and firmware.


I contacted Lenovo support and they immediately told me to send it in for repair (not my intention initially) since I have still some warranty left on it. In case that they are not able or willing (it’s Linux) to solve the problem, I’ll try the firmware/bios update, thanks for the proposal! In any case I’ll report back how the story went on! :slight_smile:

This is annoying, but a safe option. Wish you good luck. :crossed_fingers:
…nevertheless, fwupd, or gnome-firmware is a must.
That’s why people buy Thinkpads, even though it’s always been a bit more expensive to have good taste. :innocent:

1 Like

As far as I remember I did some firmware updates in the first few days after getting it, but looks like I didn’t keep up with new versions (or just missed the actual BIOS firmware, but I am sure that I did install some firmware related stuff).

For linux, fwupd or gnome-firmware is the way to go. With gnome-firmware you can manage it via GUI.

Update: I got the laptop back and according to the repair report they exchanged everything (PCB, that is, the motherboard, and the keyboard&trackpoint combination). The cause was an electric damage.

However, I’m a bit afraid of running the linux-firmware update now, possibly it will brick the device again. But I cannot fix the linux-firmware version on the long run, too, right?

Good news, don’t be scared as this was a hardware defect, install fwupd or gnome-firmware and let it do it’s thing.

Edit: pretty damn fast sevice, btw.

Yep, the service is indeed excellent!

It was, but maybe induced by the linux-firmware update? I mean, it appeared JUST after the update…

…do it now, then there is enough time to send it back :stuck_out_tongue_winking_eye:

In the mean time I noticed that the stylus isn’t being charged after the repair (it’s shown to be at 0% and also doesn’t work), so it looks like I will have to send it in again anyway…

I can’t think of anything right now to cheer you up. :hammer:

Well, the good thing is that if I need to send it in again, I can as well run the update!

Thanks, I appreciate the (moral) support! :grinning: