Bug 496244 - Cursor Oddity
Summary: Cursor Oddity
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 6.2.2
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-14 00:21 UTC by Matt
Modified: 2024-11-14 17:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt 2024-11-14 00:21:04 UTC
SUMMARY
When using the Breeze cursor theme, the mouse cursor dramatically increases in size when hovering over terminal windows (including Ptyxis 47.3 and other terminal emulators) specifically on the secondary monitor. The cursor returns to normal size when moved away from the terminal window.

STEPS TO REPRODUCE
1. Set up dual monitors in Wayland session
2. Set cursor theme to Breeze
3. Open any terminal emulator on the secondary monitor
4. Move cursor over the terminal window

OBSERVED RESULT
Cursor becomes significantly larger when hovering over terminal windows
Issue only occurs on the secondary monitor
Issue only occurs with terminal applications (from what I've experienced)
Cursor returns to normal size when moved away from terminal windows

EXPECTED RESULT
Cursor should maintain consistent size across all windows and monitors

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Aurora-DX & Bazzite (Fedora 41)
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0-1
Qt Version: 5.15.15-1

ADDITIONAL INFORMATION
Both monitors are set to 100% scaling
Issue does not occur with other cursor themes (verified with High Contrast theme)
Issue persists across different terminal emulators
Issue is specific to terminal applications; several other applications did not trigger this behavior
Comment 1 Nate Graham 2024-11-14 17:19:01 UTC
That's a signal that the app doesn't implement the cursor-shape-v1 Wayland protocol, which exists to prevent issues like this (among other things). I'd recommend reporting it to that app's developers.