No wm_class on Gnome Wayland

[flexagoon]

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

20240811_112922_0ac1e948

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

When launching Wezterm, it has no wm_class, even when using the wezterm start --class command.

To Reproduce

1. Run wezterm
2. Check it's wm_class
3. It's null

Configuration

no config

Expected Behavior

wm_class should have a default value according to the docs, or it should be set to the value of the --class option

Logs

No response

Anything else?

No response

[ghost]

Could this be related with my inability to drag around and resize the window on a fresh Fedora 40 Gnome installation?

After including the following line: config.enable_wayland = false

xprop could appropriately target the wezterm window and provide with information, including a wm_class. That also fixed my issue.

[flexagoon]

@makoten

Could this be related with my inability to drag around and resize the window on a fresh Fedora 40 Gnome installation?

This can be fixed by using window_decorations = "RESIZE", but for me this option is also broken on nightly, resulting in an infinitely large window frame.

None of this happens on the stable version for me

[jdoss]

I am seeing this when I have the following set too:

config.enable_wayland = true
config.window_decorations="RESIZE"

And I can't resize the window at all..

Setting config.enable_wayland = false allows for the window to be resized but it gets the window decorations.

This is on a fresh Fedora 40 install in Gnome with Wayland on wezterm-20240812_215703_30345b36-0.x86_64

[benjaminglass1]

Replying just to note that I reproduce this on a fresh Fedora 40 Gnome Wayland install as well, using yesterday's nightly.

[nezia1]

#4962 is very likely related. Having the same issues, seems like they're completely re-implementing Wayland support.