-
-
Notifications
You must be signed in to change notification settings - Fork 763
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
Panic with Wayland #4948
Comments
I have the same issue on Sway 1.9-RC2. Here is a full BACKTRACE from a build off main just now.
|
Thanks, can you run wezterm like this:
and share what gets logged? |
This avoids a nasty panic, and shows some more context, but doesn't really fix anything. refs: #4948
This is the only additional information displayed on the console before the trace with that set: 22:01:22.958 TRACE window::connection > Screens { main: ScreenInfo { name: "DP-3", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }, active: ScreenInfo { name: "DP-3", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }, by_name: {"DP-3": ScreenInfo { name: "DP-3", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }, "DP-2": ScreenInfo { name: "DP-2", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }}, virtual_rect: Rect(1920x1200 at (0, 0)) } |
Thanks; so I think this is because the frame is hidden because there are no client-side decorations. |
That changed something but it still panics. Now I briefly see a wezterm window that is not sized correctly in the frame before the panic at the same place in simthay-client-toolkit. 22:09:05.337 TRACE window::connection > Screens { main: ScreenInfo { name: "DP-3", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }, active: ScreenInfo { name: "DP-3", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }, by_name: {"DP-3": ScreenInfo { name: "DP-3", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }, "DP-2": ScreenInfo { name: "DP-2", rect: Rect(1920x1200 at (0, 0)), scale: 1.0, max_fps: None, effective_dpi: Some(96.0) }}, virtual_rect: Rect(1920x1200 at (0, 0)) } |
I just updated my nighly from Copr on Fedora 39 and hit same issues
|
This is the output I get running from latest commit
|
I think |
This has stopped the abort panic, now in GNOME I am not getting the resize bar on the window. When I type anything inside the wezterm window, it prints an error line for each character For reference my system details are all listed in #4825
|
I am getting the same cursor error and the cursor does not change or completely vanishes when moving over the wezterm window. |
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
KDE Plasma
WezTerm version
wezterm 20240203-152124-a4356069
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
WezTerm crashes on start, probably related to #4777
To Reproduce
No response
Configuration
Expected Behavior
WezTerm starts
Logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: