Bug 463534

Summary:	Gtk cursors problematic on Wayland
Product:	[Plasma] kwin	Reporter:	tusooa <tusooa>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	kde
Priority:	NOR
Version:	5.26.4
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description tusooa 2022-12-27 22:00:27 UTC

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open xournalpp
2. Change tool to pen, draw something
3. Hover on anywhere other than the canvas

OBSERVED RESULT
The cursor is shown as a dot.

EXPECTED RESULT
The cursor is shown normally, with the default cursor.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.18.12 / 5.26.4
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION

Comment 1 David Edmundson 2023-01-04 13:21:38 UTC

Are you able to test on any other compositors?

When I run this I see lots of gtk warnings about icon themes not being found. I do end up with a fallback boring cursor being used rather than a dot, but that's going to be setup specific. If kwin gets told to draw a dot, we'll draw a dot.

Comment 2 tusooa 2023-01-04 18:18:50 UTC

(In reply to David Edmundson from comment #1)
> Are you able to test on any other compositors?
> 
> When I run this I see lots of gtk warnings about icon themes not being
> found. I do end up with a fallback boring cursor being used rather than a
> dot, but that's going to be setup specific. If kwin gets told to draw a dot,
> we'll draw a dot.

The dot is xournalpp-specific -- it is the cursor of it when it is drawing something. However, this cursor should not appear outside the canvas.

On other gtk programs (firefox, emacs) the cursors seem weirder and sometimes disappear.

I ran xournalpp on weston, and yes I can reproduce it there. Maybe it's a gtk bug?

Comment 3 tusooa 2023-01-04 18:24:12 UTC

Ok it's an issue of https://gitlab.gnome.org/GNOME/gtk/-/issues/5379 (I'm not sure whether gtk is an upstream or downstream, if I'm wrong please correct me)