Skip to content
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

Hyprland, crash on monitors with scale > 1 #5406

Open
diegoroccia opened this issue May 10, 2024 · 2 comments · May be fixed by #6508
Open

Hyprland, crash on monitors with scale > 1 #5406

diegoroccia opened this issue May 10, 2024 · 2 comments · May be fixed by #6508
Labels
bug Something isn't working

Comments

@diegoroccia
Copy link

diegoroccia commented May 10, 2024

What Operating System(s) are you seeing this problem on?

Linux Wayland

Which Wayland compositor or X11 Window manager(s) are you using?

Hyprland 0.40.0

WezTerm version

wezterm 20240510-062420-e19def7c

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 is not starting on monitors where scale > 1.

I have 3 monitors

❯ hyprctl monitors -j | jq -r '.[] | [ .id, .name, .scale ]| @csv'
0,"eDP-1",1.50
1,"DP-3",1.00
2,"DP-4",2.00

when starting on DP-3, it works

when starting on the other 2 monitors, it crashes with

16:40:12.144  WARN   wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 35, cols: 101 }) because window_state is MAXIMIZED
xdg_surface@29: error 3: xdg_surface has never been configured
Protocol error 3 on object xdg_surface@29: 
16:40:12.180  ERROR  wezterm_gui                     > running message loop: Protocol error 3 on object xdg_surface@29: ; terminating

If I start it on the monitor that works and then move it over to another monitor, it crashes

I saw other reports, but they were all closed, or they were mentioning additional informations that didn't reflect my case

I tried changing the monitor scale to 1 on all 3 monitors and all works well

To Reproduce

No response

Configuration

local wezterm = require("wezterm")
local config = wezterm.config_builder() or {}

config.enable_wayland = true

-- don't care about tabs
config.enable_tab_bar = false
config.use_fancy_tab_bar = false
config.show_tabs_in_tab_bar = false
config.show_new_tab_button_in_tab_bar = false

-- colorscheme
config.color_scheme = "Catppuccin Mocha"

config.font = wezterm.font_with_fallback({
	{
		family = "JetBrains Mono",
		weight = "Regular",
		harfbuzz_features = { "calt=1", "clig=1", "liga=1" },
	},
	{ family = "Noto Color Emoji", weight = "Regular" },
})

config.line_height = 1.4
-- config.underline_position = "-20px"
config.underline_thickness = "200%"
config.command_palette_font_size = 12

config.window_padding = {
	left = 20,
	right = 20,
	top = 20,
	bottom = 20,
}

config.keys = require("keys")

config.default_prog = { "tmux" }

return config

Expected Behavior

No response

Logs

No response

Anything else?

No response

@diegoroccia diegoroccia added the bug Something isn't working label May 10, 2024
@MaeIsBad MaeIsBad linked a pull request Dec 22, 2024 that will close this issue
@MaeIsBad
Copy link

@diegoroccia would you mind trying out this PR?
#6508

@MaeIsBad
Copy link

(or anyone else who might have had the same issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants