Double mouse pointer when at rest

English Applications
1

Since Thursday last week I’m having a problem with my mouse pointer. Once the pointer is stationary for about five seconds, a double appears about 2cm to the right.

Have a look: https://rotjes.bangblog.eu/OpenSUSE/185117-mouse_pointer/20250519_090326.mp4

I am using Tumbleweed and KDE.

Hardware:
7800X3d
X670E ProAart
AMD RX 7800 XT
64 GB DDR5

I have tried changing mouse pointers, but to no avail.
I normally use X11, but I also tried wayland and that makes no difference.

Any tips on how to fix this?

2 Likes
2

So, anything interesting happen last Thursday that you are aware of that may have resulted in this problem? (software update, hardware changes, driver change, GUI setting change?).

Here’s an easy troubleshooting exercise… create a new user account. Log out of your usual user account, then log in as the new user. Do.ypu see the same mouse problem?

3

I had a new motherboard and CPU the week before, but I had no problems initially. I update a couple of times a week. IIRC it happened after an update.

I tried making a test account, it also shows the same behaviour. While I didn’t notice it before, I just saw it happen on the login screen as well.

4

That is a strange issue for sure. I’m not aware of similar current reports to date.

It might be useful to share detailed graphics information:

inxi -SGaz

Which SDDM theme are you using (in case that is related somehow)?

cat /etc/sddm.conf.d/*

or

journalctl -b | grep -i "theme"
5 
onno@tigershark*2025-05-19T11:43:35+0200:/home/onno> inxi -SGaz
System:
  Kernel: 6.14.6-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.14.6-1-default
    root=UUID=2170e271-d925-4ed9-8d1e-ba0aced488eb splash=silent
    mitigations=auto quiet security=apparmor
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
    wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
    Tumbleweed 20250515
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 32 [Radeon RX 7700 XT /
    7800 XT] vendor: ASRock driver: amdgpu v: kernel arch: RDNA-3
    code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1,
    Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:747e class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: ASUSTeK
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none
    empty: DP-4, DP-5, HDMI-A-2, Writeback-2 bus-ID: 6d:00.0
    chip-ID: 1002:164e class-ID: 0300 temp: 38.0 C
  Device-3: Intel RealSense SR300 driver: uvcvideo type: USB rev: 3.1
    speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 6-2.1:3 chip-ID: 8086:0aa5
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
    s-diag: 1165mm (45.88")
  Monitor-1: DP-2 model: Acer CG437K P serial: <filter> built: 2021 res:
    mode: 3840x2160 hz: 120 scale: 100% (1) dpi: 104 gamma: 1.2
    size: 941x529mm (37.05x20.83") diag: 1080mm (42.5") ratio: 16:9 modes:
    max: 3840x2160 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: radeonsi device: 2 drv: swrast gbm: drv: kms_swrast
    surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.5 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 7800 XT (radeonsi navi32 LLVM
    20.1.4 DRM 3.61 6.14.6-1-default) device-ID: 1002:747e memory: 15.62 GiB
    unified: no
  API: Vulkan v: 1.4.309 layers: 5 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7800 XT (RADV NAVI32) driver: N/A device-ID: 1002:747e
    surfaces: xcb,xlib device: 1 type: integrated-gpu name: AMD Radeon
    Graphics (RADV RAPHAEL_MENDOCINO) driver: N/A device-ID: 1002:164e
    surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe (LLVM 20.1.4 256
    bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: radeontop wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

onno@tigershark*2025-05-19T11:43:40+0200:/home/onno> cat /etc/sddm.conf.d/*
[Autologin]
Relogin=false
Session=default.desktop
User=

[General]
HaltCommand=
RebootCommand=

[Theme]
Current=maldives

[Users]
MaximumUid=60000
MinimumUid=1000

Is this any help?

6

Interesting setup with two AMD graphics devices. Let’s see what others come back with.

7

Are you using fractional scaling?

1 Like
8

I wasn’t. But just to be sure I fiddled with the setting a bit and now the problem is no longer present when logged in. The login screen still has this problem though. But that is nowhere near as annoying as having it while logged in.

9

Since AM5 AMD Ryzen CPU’s have an iGPU by default.

10

Try disabling the iGPU in the BIOS. Also, there is a way to specify the default GPU to use. But you’ll have to hunt for the details unless someone comes along and posts it.

11

I am having this exact same issue and here is a fun one.

Had a dual booted PC with Windows and TW. No issues. I decided to nuke everything and switch to TW full time so I did a clean wipe and re installation of TW and now, I too, have this issue. Happened last week. Reinstalled a few times as well to see if it was a issue with the installation.

I cant figure this out either. I have tried X11 and Wayland and there is no difference.

iGPU is disabled.
7900XTX GPU
7900X CPU
B650M Aorus Elite AX.

12

@Clubby Well, that means it might be a bug after all.

For me this is now no longer as annoying as it was when it was also happening on the desktop, so I’m not really going to put in more time to fix the login screen, but I’ll answer questions if there are any.

13

Do you have a graphics tablet?

I found this post.

I still don’t understand what genius (/s) reason is behind the decision to give graphics tablets their own cursor (in Wayland specs). As far as I know this is new and unique to Wayland - it’s not in X, nor Windows nor macOS, and it defies expectations regarding how a drawing tablet works. It allows a mouse pointer and a tablet pointer to exist at the same time - literally no one expects that or uses both at once.

https://www.reddit.com/r/kde/comments/18ggn30/shortcomings_and_regressions_in_plasma_6_wayland/

14

So just to clarify that you’re not experiencing the double cursor issue now? What did you change specifically?

15

Not while logged in. It disappeared after fiddling with the settings for fractional scaling. It was set to 100% and I set it to 125% and back to100% again and ever since it is no longer happening while logged in. It still happens when nobody is logged in, but that is something I can live with.

16

This bug is happening to me as well. The fractional scaling settings are at default and changing them and then back does nothing for me. And I have no iGPU in my system. I use Wayland. The bug occurs with or without Adaptive Sync on. Interestingly the bug cannot be screenshotted for me, it does not appear on the screenshot.

I also have only one monitor (but I use 4 virtual desktops), which seemed to be the assumed main culprit in the identical bug identified over on the KDE bug board (I guess I should post over there as well): 504239 – Duplicate cursor appears after mouse is idle for a couple seconds, if multiple monitors using different resolutions are connected

Hardware (unsure what is important, but I’ll list what those previous has):
CPU: Ryzen 7 5700X3D
GPU: Radeon RX 7800 XT
MB: MSI B450M Mortar Titanium
RAM: 32 GB DDR4

1 Like
17

Oh, and importantly this is an intermittent problem, occurring seemingly randomly and sometimes not occurring at all for longer periods of time. I am trying to figure out if there is a pattern to when it occurs, but so far I have been unable to.

1 Like
18

Ran into the same problem here. Not intermittent as far as I can tell, it’s always happening with the cursor at rest, and the system is always shutdown over night.

System:
  Kernel: 6.14.6-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: initrd=\opensuse-tumbleweed\6.14.6-1-default\initrd-8627c7c0d5ba64a58162d5f193da2ed6b8e60086
    splash quiet amd_pstate=active
    cryptdevice=UUID=328cd45c-7d78-4964-bff3-dc1db145844e:system-root
    root=UUID=1c74c27f-a748-4a5c-a602-3c67f545ed8f mitigations=auto
    rootflags=subvol=@/.snapshots/1027/snapshot
    systemd.machine_id=14fa0dc0f8064fb687ee0823e2018501
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A info: frameworks v: 6.14.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
    Tumbleweed 20250515
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 32 [Radeon RX 7700 XT /
    7800 XT] vendor: XFX driver: amdgpu v: kernel arch: RDNA-3 code: Navi-3x
    process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, Writeback-1
    bus-ID: 0d:00.0 chip-ID: 1002:747e class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: DP-2 model: AOC AG273QS3R4 serial: <filter> built: 2020 res:
    mode: 2560x1440 hz: 165 scale: 100% (1) dpi: 109 gamma: 1.2
    size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.5 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 7800 XT (radeonsi navi32 LLVM
    20.1.4 DRM 3.61 6.14.6-1-default) device-ID: 1002:747e memory: 15.62 GiB
    unified: no display-ID: :0.0
  API: Vulkan v: 1.4.309 layers: 9 device: 0 type: discrete-gpu name: AMD
    Radeon RX 7800 XT (RADV NAVI32) driver: N/A device-ID: 1002:747e
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
    20.1.4 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: lact,radeontop wl: wayland-info
    x11: xdpyinfo, xprop, xrandr

Single display, single GPU, Wayland, no touch input devices. 2 virtual desktops.
Messing around with most display options (scaling etc.) does nothing, but setting the display to a non-native 1080p does fix it while in that resolution, but the issue returns as soon as it switches back to native 1440p.

1 Like
19

This issue happens with me too! I have my system rolled back to 20250508 and it seems to be working ok in there.

  • CPU: 7800x3D
  • GPU: Radeon 7800XT
  • MB: Gigabyte Aorus B650 Elite AX
  • Kernel Version (at the moment): 6.14.5

Judging by specs reported by other people in comments, could this be an AMD specific issue?

1 Like
20

It absolutely could be connected to AMD GPUs. I have an Intel ARC A750 and have other glitches, but I’ve never had the double cursor. They’re doing a lot of work on HDR and other things related to the display so there could be a bug in KDE or maybe it’s more related to the AMD driver.

You guys who have that hardware are the users they need to help track it down, or rule out an AMD only issue.

One thing you can do is go into System Settings and turn off Effects one at a time and see if it’s one of the effects. If it is it’s probably your favorite effect. :thinking: :grin: