New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad appearance on wayland #5349
Comments
Same issue. |
Same errors with |
I have the same experience after the recent update of my arch. I also have the same issue with kitty. This is the related issue: kovidgoyal/kitty#7396 |
Probably closely related or even the same bugg as #5360, I'm experiencing both issues dependending on the display layout and the runtime config. Probably related to gnome 46 or mutter itself. I think that kitty issue is a red herring tho', tried messing with all the ime settings sadly without any success. Also explicitly disabling wayland |
It should have nothing to do with gnome46. This problem has already appeared in January. But I not reported it. Instead, I switched to kitty. In the change log at that time, I mainly talked about "reconstructing wayland". I suspect that it was related to that reconstruction. |
Please try the most recent nightly build |
since 20240505_232355_e6db4408, the gui.get_appearance() function already be fixed, but window bug still live. for the master(f6fdfeb)
if wezterm starts with: return {
window_decorations = "INTEGRATED_BUTTONS|RESIZE",
} then wezterm just like before: |
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
wezterm 20240405_180910_cce0706b
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
the first is :
seconds is:
wezterm.gui.get_appearance always return 'Light'.
This screenshot shows some errors, but I don't think they are important. Because wezterm just caused gnome to restart. This problem occurred after
These two problems first appeared in updates after January this year.
To Reproduce
No response
Configuration
Expected Behavior
just like last year
Logs
Anything else?
no
The text was updated successfully, but these errors were encountered: