Blurry mouse pointer on Wayland

[filipwiech]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

I have the following setup:

• Ubuntu 24.04 GNOME Wayland
• Main laptop screen, 100% scaling
• External 4K monitor, set to 200% scaling

When I move Zed onto the 4K screen, the window is scaled nicely (correct size and crisp graphics), however whenever I move the mouse pointer over the editor it becomes blurry. It has the correct size, but it's as if the icon used for the rendering came from a lower resolution asset. If I move the pointer outside of the Zed window (for example over the desktop or some other application) then it becomes sharp. Sorry for no images, but unfortunately it doesn't show on screenshots.

Environment

Zed: v0.141.0 (Zed Nightly d4891a6)
OS: Linux Wayland ubuntu 24.04
Memory: 31 GiB
Architecture: x86_64

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

Zed.log

[notpeter]

Can you try the commands shown in #14862 to see if that helps?

[senonide]

Same problem with this setup:

• Fedora 40 Gnome Wayland
• Laptop screen 2880x1920p, 200% scaling
• Zed v0.148.1

Only when I move the mouse pointer over the editor, it becomes blurry. It seems that the problem comes from scaling at 200% because this does not happen when the screen is at a scaling factor of 100%.

Can you try the commands shown in #14862 to see if that helps?

I tried it but it doesn't fix the problem. I am already using the default cursor in Fedora (Adwaita)

[apricotbucket28]

I believe the issue here is that when we set the cursor surface for the pointer we don't actually specify the buffer scale for said wl_surface.
Here's SCTK code for reference: https://github.com/Smithay/client-toolkit/blob/c583de8dd5651f8168c6513cd282137c42aae049/src/seat/pointer/mod.rs#L458-L495

[Raiden0456]

I've just encountered this issue, mouse pointer was definitely fine a week ago. Is this an ongoing issue?