After KDE 6.1 update, Cursor size increases while moving mouse

After KDE 6.1 update, Cursor size increases while moving mouse, and then defaults to normal size when not moving.

╰─λ garuda-inxi
System:
Kernel: 6.9.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=bb707c09-cee2-492b-b609-ae39702a15e8 rw rootflags=subvol=@
quiet loglevel=3 mitigations=off ibt=off
Desktop: KDE Plasma v: 6.1.0 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: JINYUE product: X99 v: N/A
serial: <superuser required>
Mobo: JINYUE model: JINYUE TITANIUM D3 serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends v: 5.11
date: 11/18/2021
CPU:
Info: model: Intel Xeon E5-2698B v3 bits: 64 type: MT MCP arch: Haswell
level: v3 note: check built: 2013-15 process: Intel 22nm family: 6
model-id: 0x3F (63) stepping: 2 microcode: 0x49
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 4 MiB desc: 16x256 KiB
L3: 40 MiB desc: 1x40 MiB
Speed (MHz): avg: 3386 high: 3400 min/max: 1200/3400 scaling:
driver: intel_cpufreq governor: performance cores: 1: 3400 2: 3400 3: 3400
4: 3400 5: 3400 6: 3400 7: 3400 8: 3400 9: 3400 10: 3400 11: 3400 12: 3400
13: 3400 14: 3400 15: 3400 16: 3400 17: 2964 18: 3400 19: 3400 20: 3400
21: 3400 22: 3400 23: 3400 24: 3400 25: 3400 26: 3400 27: 3400 28: 3400
29: 3400 30: 3400 31: 3400 32: 3400 bogomips: 127985
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Tul / PowerColor Red Devil 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: DP-1,HDMI-A-1
empty: DP-2,DP-3,Writeback-1 bus-ID: 05:00.0 chip-ID: 1002:73df
class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu d-rect: 3840x1080 display-ID: 0
Monitor-1: DP-1 pos: primary,left res: 1920x1080 size: N/A modes: N/A
Monitor-2: HDMI-A-1 pos: right res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi
navi22 LLVM 17.0.6 DRM 3.57 6.9.5-zen1-1-zen) device-ID: 1002:73df
memory: 11.72 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 9 device: 0 type: discrete-gpu name: AMD
Radeon RX 6700 XT (RADV NAVI22) driver: mesa radv v: 24.1.1-arch1.1
device-ID: 1002:73df surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.1.1-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
class-ID: 0403
Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-3: Logitech Blue Microphones
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
lanes: 1 mode: 2.0 bus-ID: 3-10:6 chip-ID: 046d:0ab7 class-ID: 0300
serial: <filter>
API: ALSA v: k6.9.5-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.7 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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
bus-ID: 09:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 824.93 GiB used: 274.05 GiB (33.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 35.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 250GB
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Gigabyte model: GP-GSTFS31120GNTD
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 11.3 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: HM250HI
size: 232.88 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: N/A serial: <filter> fw-rev: 01C4 scheme: MBR
ID-5: /dev/sdd maj-min: 8:48 vendor: SanDisk model: Ultra Fit
size: 14.48 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 111.49 GiB size: 111.49 GiB (100.00%)
used: 18.62 GiB (16.7%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 111.49 GiB size: 111.49 GiB (100.00%)
used: 18.62 GiB (16.7%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 111.49 GiB size: 111.49 GiB (100.00%)
used: 18.62 GiB (16.7%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 111.49 GiB size: 111.49 GiB (100.00%)
used: 18.62 GiB (16.7%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.24 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 40.0 C mobo: N/A gpu: amdgpu temp: 43.0 C
mem: 44.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 1068
Info:
Memory: total: 32 GiB available: 31.24 GiB used: 3.77 GiB (12.1%)
Processes: 516 Power: uptime: 9m states: freeze,mem,disk suspend: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 12.48 GiB services: org_kde_powerdevil, power-profiles-daemon,
upowerd Init: systemd v: 256 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1462 libs: 467 tools: octopi,paru Compilers:
gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-06-18
Last full system update: 2024-06-21
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

How the f am i getting theese bugs :smiley:
I’m just gonna revert 6.0.5 :smiley:

This isn’t a bug, this is a new feature added to 6.1 for people who have trouble finding their cursor, especially on higher resolutions. You simply need to disable it in the accessibility settings.

5 Likes

I was about to ask, if this was intended in 6.1 omg. :melting_face:

But why it keeps increasing, who needs that xD

Thx @NuclearDragon, linux is to hard for me i guess :smiley:

3 Likes

I thought it was a bug XD, but thank you all

1 Like

I have seen this listed as feature, as @NuclearDragon mentioned. I presume if you have, for example, 2x 4K monitors and a laptop screen, the cursor is tiny, so you shake it to find where it is. Supposedly MacOS has this, but what do I know.
The cursor:

image

1 Like

macs have it, it was in kde before but was located in window behavior

So, as I understand it, this feature was previously opt-in, now it is opt-out (on by default).

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.