Are you talking about the mouse pointer or the text cursor? (the former is handled by the Wayland compositor, ie gnome-shell/mutter rather than gtk+)

FWIW, mouse pointer scaling works fine here (mutter-3.26.2) and adjusts to the output scale.

Just tested the text cursor, it's scaled as well, along with the rest of the window.

I'm talking about the mouse pointer. On Wayland it's drawn by the compositor, but it's set by the client and drawn based on the properties set on the surface. For a scaled output that should be a 2x buffer and a surface with scale=2 set.

To reproduce this I use rootston, the reference compositor for wlroots: https://github.com/swaywm/wlroots

It's entirely possible the bug is on our side, but I suspect that's not the case.

OK, I see the cursor being "truncated" in weston when output scale=2

(In reply to Olivier Fourdan from comment #4)
> OK, I see the cursor being "truncated" in weston when output scale=2

Yet I am still not convinced this is a client issue, the problem doesn't show if I run "weston --use-pixman".

Besides, looking at the WAYLAND_DEBUG logs, I can tell the scale is set as expected:

  -> wl_pointer@3.set_cursor(1020, wl_surface@12, 3, 3)
  -> wl_surface@12.attach(wl_buffer@22, 0, 0)
  -> wl_surface@12.set_buffer_scale(2)
  -> wl_surface@12.damage(0, 0, 24, 24)
  -> wl_surface@12.commit()

So as far as I can tell, gdk wayland backend is doign the fight thing and it works with gnome-shell/mutter and weston (using the pixman backend).

Alright, I'll investigate further on my end and get back to you.

This is indeed our bug, sorry for the trouble.