Wezterm wont start on Hyprland

[rabiescow]

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.48.1 built from branch at commit 29e2e59fdbab8ed2cc23a20e3c6043d5decb5cdc

WezTerm version

wezterm 20240203-110809-5046fc22

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

I saw issue #5301 that was closed but seems to still be an issue.

Both are latest versions in the AUR.

When running wezterm with default config I get the following:

It works if I disable wayland in the config but thought you guys should know that it is still happening.

To Reproduce

Install wezterm and hyprland from AUR, run without any config.

Configuration

Default.

Expected Behavior

For the program to start.

Logs

13:19:12.309 ERROR wezterm_term::terminalstate::performer > kitty_img: data should have been materialized in coalesce_kitty_accumulation: base64 decode: Invalid padding

Anything else?

No response

[bew]

The error you see in the logs indicates that an image is trying to be displayed via the Kitty protocol. That image is probably part of your shell configuration, maybe via a neofetch or similar? Try to disable that, see if it improves.

Also, can you indicate which version of nightly you tried? the version you mentioned is the last stable version from ~a year ago.

[BluewyDiamond]

for me the latest git commit works normally while the latest 2024 release doesn't

[briheet]

Issue is when you install it via sudo pacman -S wezterm which is this ver := wezterm-20240203.110809.5046fc22-2 It is working with yay -S wezterm-git which is this ver := wezterm-git-20240922.091625.5a594f51-3 Also, the working wezterm version is this := wezterm 20250510-175818-7ee60e2d

[edbar42]

Issue is when you install it via sudo pacman -S wezterm which is this ver := wezterm-20240203.110809.5046fc22-2 It is working with yay -S wezterm-git which is this ver := wezterm-git-20240922.091625.5a594f51-3 Also, the working wezterm version is this := wezterm 20250510-175818-7ee60e2d

This worked for me as well. Thank you.

[c02y]

I'm using wezterm-git 20250604.060157.5106c8c1-1 on Archlinux, it won't start on hyprland, error message is:

18:10:39.568  WARN   window::os::wayland::connection > Unable to resolve appearance using xdg-desktop-portal: get_appearance.read_setting: Reading xdg-portal org.freedesktop.appearance color-scheme: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
18:10:39.706  WARN   wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 57, cols: 120 }) because window_state is MAXIMIZED
wp_linux_drm_syncobj_surface_v1#30: error 4: Missing acquire timeline
Protocol error 4 on object wp_linux_drm_syncobj_surface_v1@30:
18:10:39.709  ERROR  wezterm_gui                     > running message loop: Protocol error 4 on object wp_linux_drm_syncobj_surface_v1@30: ; terminating

Any idea?

[nikbrunner]

I'm using wezterm-git 20250604.060157.5106c8c1-1 on Archlinux, it won't start on hyprland, error message is:

18:10:39.568  WARN   window::os::wayland::connection > Unable to resolve appearance using xdg-desktop-portal: get_appearance.read_setting: Reading xdg-portal org.freedesktop.appearance color-scheme: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
18:10:39.706  WARN   wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 57, cols: 120 }) because window_state is MAXIMIZED
wp_linux_drm_syncobj_surface_v1#30: error 4: Missing acquire timeline
Protocol error 4 on object wp_linux_drm_syncobj_surface_v1@30:
18:10:39.709  ERROR  wezterm_gui                     > running message loop: Protocol error 4 on object wp_linux_drm_syncobj_surface_v1@30: ; terminating

Any idea?

Having the exact same problem. wezterm 20250604-060157-5106c8c1

[c02y]

I'm using wezterm-git 20250604.060157.5106c8c1-1 on Archlinux, it won't start on hyprland, error message is:

18:10:39.568  WARN   window::os::wayland::connection > Unable to resolve appearance using xdg-desktop-portal: get_appearance.read_setting: Reading xdg-portal org.freedesktop.appearance color-scheme: org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
18:10:39.706  WARN   wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 57, cols: 120 }) because window_state is MAXIMIZED
wp_linux_drm_syncobj_surface_v1#30: error 4: Missing acquire timeline
Protocol error 4 on object wp_linux_drm_syncobj_surface_v1@30:
18:10:39.709  ERROR  wezterm_gui                     > running message loop: Protocol error 4 on object wp_linux_drm_syncobj_surface_v1@30: ; terminating

Any idea?

Having the exact same problem. wezterm 20250604-060157-5106c8c1

Try to set config.enable_wayland = false in ~/.config/wezterm/wezterm.lua, I can start wezterm in Hyprland, it is using xwayland though.

[raulcesar]

I was having this problem as well. When running version 20240203.110809.5046fc22-2 (from arch package). I was able to run it if i did: hyprctl dispatch exec "[float;tile] wezterm"

I downloaded source code from git, and compiled from source, generating version "20251005-110037-db5d7437". This version ran without problems in wayland.

[bew]

Interesting, could others try the latest nightly/git version see if they still have a start failure or not? @c02y @nikbrunner @edbar42 @briheet @rabiescow (let's wait for 2-3 good report before closing this, if successful)

We recently merged a PR (#7277) to fix a sizing issue on hyprland, which might be related somehow 🤔

[raulcesar]

Hey, just as added info, I got home and just tried out the git version. On my work computer I had compiled it directly from git repo (with cargo), but to change it up a bit, at home I built and installed it from the Arch AUR.

My home computer was still running version 20240203.110809.5046fc22-2, and was still presenting the same problem.

My home and work computer have very similar configurations. Both run arch with hyprland and are pretty much up to date.

checked the AUR version to make sure it was the same commit as the one I used on work computer, and it was: "db5d7437389eac5f63ad32e3b50d95b2b86065d1".

Sure enough, the AUR version also worked fine at home. So I would wager the bug got fixed.

[c02y]

@bew

Just tried the wezterm-git 20251005.110037.db5d7437-1 build from archlinuxcn repository.

I works OK without using config.enable_wayland = false config, and it is native instead of xwayland: 1 on Hyprland.

[iainsimmons]

I had this issue for a while until I removed the following (which I had carried over from my macOS config):

config.front_end = "WebGpu"
config.webgpu_power_preference = "HighPerformance"

Now it works fine, even without config.enable_wayland = false, though having that makes the font rendering change to look closer to what I see in kitty and other terminals.