Very slow startup (>1.5s)

[murrrda]

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

Linux X11

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

i3wm with picom

WezTerm version

20240730-082727-56a27e93

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 startup speed of WezTerm is inconsistent and appears to be random. It can be either very slow or okay, regardless of whether an existing instance is already running.

To Reproduce

No response

Configuration

-- Pull in the wezterm API local wezterm = require("wezterm")

-- This will hold the configuration. local config = wezterm.config_builder()

-- config config.max_fps = 165

-- font config.font = wezterm.font("JetBrains Mono") config.font_size = 16 config.line_height = 1.1

-- and finally, return the configuration to wezterm return config

Also happens without config

Expected Behavior

No response

Logs

Debug Overlay wezterm version: 20240730-082727-56a27e93 x86_64-unknown-linux-gnu Window Environment: X11 i3 Lua Version: Lua 5.4 OpenGL: Mesa Intel(R) Graphics (ADL GT2) 4.6 (Compatibility Profile) Mesa 24.1.4 Enter lua statements or expressions and hit Enter. Press ESC or CTRL-D to exit 01:01:12.790 WARN window::os::x11::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 01:04:44.592 ERROR wezterm_mux_server_impl::local > writing pdu data buffer: Broken pipe (os error 32)

Anything else?

WEZTERM_LOG=trace wezterm start echo hi

I don't have problems with other terminals (kitty, alacritty). I also have discrete nvidia gpu RTX 3050ti.

My picom.conf: backend = "glx"; glx-no-stencil = true; glx-copy-from-front = false; xrender-sync-fence = true; vsync=true

dbe = false;

[tekul]

I had a similar issue with a delay around that warning message, but I don't see it anymore if I build from the source (a debug or release build are both fine). Maybe it is related to the fix for #5802?

[raknos13]

Same issue, switched to wezterm because kitty had font rendering issues, but wezterm is just too slow to start taking at least > 1.5s to spawn.

[raknos13]

Same issue, switched to wezterm because kitty had font rendering issues, but wezterm is just too slow to start taking at least > 1.5s to spawn.

I decided to give it another shot. So I removed the wezterm package from extras repo and installed wezterm-git from the AUR as it was more up to date and it starts up just fine now! YAY!!