GNOME Bugzilla – Bug 775217
Warning message "gdkcursor-wayland.c:170: Unable to load blank_cursor from the cursor theme" when hiding cursor under Wayland
Last modified: 2017-10-27 16:07:30 UTC
Running gnome-terminal-3.22.1-1.fc25.x86_64 under Wayland, a warning message is logged to the journal every time I start typing, and gnome-terminal tries hides the cursor (hiding works though). The exact message is
nov. 28 11:24:34 alu gnome-terminal-: gdkcursor-wayland.c:170: Unable to load blank_cursor from the cursor theme
I'm also experiencing this behaviour.
This looks to me like a bug in gdkcursor-wayland.c.
_gdk_wayland_display_get_cursor_for_name_with_scale() checks for some special cursor names (including blank_cursor) before calling _gdk_wayland_cursor_update(), but the functions _gdk_wayland_display_update_cursors() and _gdk_wayland_cursor_set_scale() do not.
Created attachment 349742 [details] [review]
wayland: Don't spew warnings for blank cursors
We were unnecessarily spewing warnings when blank cursors
were getting a new scale set. Standardize on "none" as the
name for blank cursors, and avoid the warning.
This should fix it. Testing appreciated.
Done a minimal bit of testing of this patch and it seems to help.
What I was getting previously was
Foo: Unable to load none from the cursor theme
This seems gone with this patch in place.
We did get a downstram bug report though with this patch applied:
libgtk-3-0 version: 3.22.24-3.1
gnome-boxes version: 3.26.1-1.1
The patch `gtk3-silence-log-spew-blank-cursors.patch` is causing a SIGSEGV when
I try and use GNOME Boxes to either launch a VM with guest additions, or VNC
into another machine.
I traced it back to a g_str_equal call added by this patch inside
_gdk_wayland_cursor_set_scale -- It would seem somehow window_cursor->name is
ending up null along the way, causing the whole house of cards to come tumbling
Attachment 349742 [details] pushed as db49d12 - wayland: Don't spew warnings for blank cursors
*** Bug 789564 has been marked as a duplicate of this bug. ***