You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Plasma 6
WezTerm version
20241104-083404-51c794ac
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 a wezterm window is moved from one display to another (scales 100% and 125%), it reappears quickly and changes size. At the same time, the window doesn't move anymore, and I have to grab it again to continue. After moving it to another monitor, everything is repeated.
To Reproduce
I launched the latest version as WEZTERM_LOG=debug wezterm -n start --always-new-process and moved it back and forth
Configuration
-n was used
Expected Behavior
I would expect the compositor to take care of it, as it was previously. Or keeping the same window size
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Plasma 6
WezTerm version
20241104-083404-51c794ac
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 a wezterm window is moved from one display to another (scales 100% and 125%), it reappears quickly and changes size. At the same time, the window doesn't move anymore, and I have to grab it again to continue. After moving it to another monitor, everything is repeated.
To Reproduce
I launched the latest version as
WEZTERM_LOG=debug wezterm -n start --always-new-process
and moved it back and forthConfiguration
-n
was usedExpected Behavior
I would expect the compositor to take care of it, as it was previously. Or keeping the same window size
Logs
resize_log.txt.gz
The outptut of
WEZTERM_LOG=debug wezterm -n start --always-new-process
Anything else?
I got it in the scope of #6341
The text was updated successfully, but these errors were encountered: