[TRACKER] Wayland issues

[Riteo]

Tested versions

• Reproducible in: 4.3.dev3 and later

System information

Linux/BSD - Wayland backend

Issue description

A new, experimental and opt-in Wayland backend got merged in 4.3.dev3.

While it got tested plenty, there are still quite a bunch of missing features and lots of things to improve, which are tracked in this issue.

Tasks

Preview Give feedback

1. Editor does not use Godot icon on Wayland (uses default Wayland icon instead) #87747
   bug platform:linuxbsd topic:editor topic:porting +4
2. Editor splash screen is massive on Wayland compared to X11 #87749
   bug platform:linuxbsd topic:editor topic:porting +4
3. Wayland: Shader TIME is unreliable (slow shaders) due to frame pacing method #87963
   bug platform:linuxbsd topic:porting topic:shaders +4
   
4. Wayland: Editor crashes trying to load any project. #88113
   bug crash needs testing platform:linuxbsd topic:porting +5
5. Editor ignores 'run/window_placement/screen' setting when 'prefer_wayland' is enabled #88151
   bug platform:linuxbsd topic:editor topic:porting +4
6. Mouse Input under Wayland misses slow movement #88246
   bug platform:linuxbsd topic:porting +3
7. GPU Particles have very slow framerate on Wayland #88248
   bug performance platform:linuxbsd topic:particles +4
8. [Wayland] Godot doesn't register inputs from graphic tablet on GNOME #88333
   bug platform:linuxbsd topic:input +3
9. Wayland: DRI_PRIME warnings raised by DetectPrimeEGL #88364
   bug platform:linuxbsd topic:porting +3
10. Eyedropper color picker not working with XWayland #88550
    bug confirmed platform:linuxbsd topic:porting +4
11. Wayland: Auto UI scale is rounded up when using fractional scaling #89257
    bug platform:linuxbsd topic:porting +3
12. [4.3.dev3+] Editor and project manager windows are always borderless when using wayland #89793
    bug platform:linuxbsd topic:porting +3
13. wayland cannot work with weston #90612
    bug platform:linuxbsd topic:porting +3
14. Wayland DisplayServer does not properly support opengl3_es rendering driver #91371
    bug crash platform:linuxbsd topic:porting +4
    
15. Unable to interact with window decorations on GNOME 46.1 Wayland with graphic tablet #91921
    bug platform:linuxbsd topic:porting +3
16. 4.3.dev - Problems with launching Godot/launching projects in a compositor with Xwayland disabled #92014
    bug platform:linuxbsd topic:porting +3
17. [4.3 beta 1] Godot Wayland produces corrupt config if language does not use '.' as decimal separator #92594
    bug needs testing platform:linuxbsd topic:editor +4
    
18. To enable Wayland, fctix5 can't switch input method #92643
    enhancement platform:linuxbsd topic:input topic:porting usability +5
    
19. With Wayland enabled Godot windows often show the wrong icon in Alt+Tab switcher in GNOME #93098
    bug platform:linuxbsd topic:porting +3
20. Borderless non-fullscreen windows with Wayland display server still have decorations #93472
    bug platform:linuxbsd topic:gui +3
21. Weird editor window behavior in Gnome Wayland with "prefer wayland" and editor scale different than 100% #93788
    bug platform:linuxbsd topic:porting +3
22. Panning visual shader editor in Wayland is not 1:1 with certain scaling settings #93981
    bug platform:linuxbsd topic:editor +3
    
23. Window doesn't resize properly when changing resolution, with "Display Server" set to "Wayland" in Project Settings #94157
    bug platform:linuxbsd topic:gui +3
    
24. Wayland: Godot v4.3 beta3 crashes when running on linux #94204
    bug crash platform:linuxbsd regression topic:porting +5
    
25. Editor window resizing on Wayland doesn't work (GNOME with tiled window) #94218
    bug platform:linuxbsd regression topic:gui +4
    
26. Godot Editor freezing after playing scene only on Wayland on Godot 4.3 Beta 3 #94228
    bug platform:linuxbsd topic:editor topic:porting +4
27. Wayland - US intl. keyboard layout incompatible with Godot #94445
    bug platform:linuxbsd topic:input topic:porting +4
28. Tripled key inputs after wake from sleep using "prefer Wayland" #95144
    bug platform:linuxbsd topic:input topic:porting +4
29. Wayland completely unreceptive to touch input #95256
    bug platform:linuxbsd topic:input topic:porting +4
30. Wayland: Window Resizing w/ Ultrawide - Wonky & Crash #92823
    bug needs testing platform:linuxbsd topic:porting +4
31. Wayland feels sluggish with Vulkan compared to OpenGL #95566
    bug performance platform:linuxbsd topic:porting +4
32. [Wayland] Versioned interfaces ignored when compiling #95830
    bug platform:linuxbsd topic:buildsystem +3
    
33. When running in Wayland, taskbar and window icons do not use Godot icon because Godot does not use a consistent app_id throughout its execution #96074
    bug platform:linuxbsd topic:porting +3
34. Mouse wheel paste doesn't work on Wayland editor #96214
    bug platform:linuxbsd topic:editor +3
35. Inconsistent Copy Behavior in Script Editor when Using Wayland Display Driver #95649
    bug platform:linuxbsd topic:editor topic:porting +4
36. Wayland Cursor custom Image don't show #96647
    bug platform:linuxbsd topic:input +3

Steps to reproduce

From the CLI: start the engine with the --display-driver wayland flag.

Alternatively, for the editor: set the run/platforms/linuxbsd/prefer_wayland editor setting to true or, for running projects, set the display/display_server/driver.linuxbsd project setting to wayland.

Minimal reproduction project (MRP)

N/A

[BiosElement]

Edit: , I am not confident it isn't a KDE related issue, but am not in a position to test it on other DE's currently.

This is an example: https://youtu.be/Xr5cmBRonls

Has anyone ran into a really strange issue where trying to resize a windowed instance of Godot under Wayland/KDE causes it to move way up off the top left edge of the screen at a massive scale? It does not replicate under X11, but it is such a strange thing I don't really have enough to file a useful report.

I am using a laptop display at 2256x1504 and a desktop monitor at 2569x1440. I have confirmed it does not matter if the second display is connected or not, the issue still occurs with only the laptop display connected.

This was all found using the git build of Godot as-of 4/8/24, it is not present in stable.

Update: I have narrowed this down to being introduced between cd4e4c0 and b926e51. Narrowing down still.
Update 2: Issue occurs with 34f284b. Issue partially occurs with 5cf6f3c, it does resize correctly but does so very slowly before crashing.

Reproducible in:
b926e51
7901a05

[Riteo]

Hi folks, sorry for the delay, I couldn't work on this stuff in the last few weeks. I just got back! :D

@Roogephy thanks for the report! I'll explain the situation a bit more thoroughly there once I get back to speed. I'll put the issue in the tracker and mark the relevant messages as "resolved" to not clutter the thread too much.

Hi @BiosElement, this issue feels quite complicated and I'm not sure how the bisected commits relate to this at all. That said, I recommend to file a dedicated issue ticket so that we can investigate further without cluttering up this thread.

[eobet]

Sorry, but does anyone else "feel" a difference between regular and "Prefer Wayland" setting? I don't know how to see the framerate of the editor, but I have a 120hz display and it feels like 20-30 when I enable Wayland (but other apps are fine and mouse gestures are super smooth too). This is using "single window mode" as well, btw.

[Riteo]

@eobet sorry for the delay.

That's quite weird. You could try running the editor directly by opening a project.godot file and pass the --print-fps flag: godot --print-fps path/to/project.godot

You should then see the framerate being printed into the standard output every few seconds.

If there's a substantial difference in framerate between the wayland and the x11 backend, please file a new ticket.

This is using "single window mode" as well, btw.

Note that, due to various reasons, the Wayland backend is forced to the single window mode for the time being. I'm researching the steps needed for a proper multi-window implementation.

If you see multiple native windows, then you're running the X11 backend through XWayland.