Open rishubn opened 9 months ago
Wayland support is currently being re-implemented in main
, this is an outstanding issue around that
Had the same problem under Fedora 40. As a workaround I "disabled wayland" in wezterm's config.
config.enable_wayland = false
Hope this helps for now
Still seeing this bug with the GNOME 47 Wayland session. Using Wezterm built today from git head.
Same issue for me.
Gentoo, Gnome 47, Mutter 47 -> Wayland
Latest git build
Had the same problem under Fedora 40. As a workaround I "disabled wayland" in wezterm's config.
config.enable_wayland = false
Hope this helps for now
Sadly this workaround is a no go on high-dpi displays with fractional scaling in wayland. e.g. in gnome. The enable_wayland just produces badly blurred font rendering in this scenario.
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Mutter
WezTerm version
20240204-213233-b03b833a
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
(Ubuntu 22.04) On wayland, wezterm spawns without window decorations. It cannot be resized or dragged with the mouse like other windows. This does not appear when I log in with X11. The cursor also changes color and shape when hovering over the wezterm window
Below is a gtk app next to wezterm, notice the missing header
To Reproduce
No response
Configuration
Expected Behavior
Have the same style and functionality as other windows in wayland
Logs
The log indicates the window gets destroyed, however it is still usable
Anything else?
No response