wezterm icon indicating copy to clipboard operation
wezterm copied to clipboard

Wezterm fails to launch randomly

Open TheTrio opened this issue 2 years ago • 13 comments

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 (kwin)

WezTerm version

20230212-103106-a5c2b1f3

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

Here's a video showing what's happening

https://user-images.githubusercontent.com/10794178/219683676-2aefdf8b-7cd2-4a77-82f1-34a9854a9083.mp4

I can see an icon for the application in my "taskbar" and a "wezterm-gui" process but no window shows up. If however I keep a wezterm window open and then start opening new windows, this doesn't happen. It only seems to happen when no existing window exists.

To Reproduce

  1. Open a different terminal emulator(probably would work with wezterm as well but just in case)
  2. Type in wezterm start --always-new-process
  3. If a window opens up, close it and keep entering the command in 2
  4. After 2 or 3 tries, the window won't open at all.

Configuration

no config

Expected Behavior

The window appears every time its launched

Logs

No response

Anything else?

No response

TheTrio avatar Feb 17 '23 14:02 TheTrio

I've been running into this myself, and one of the only workarounds I found was to disable Wayland for WezTerm. However, this makes it slow on other virtual desktops, and I'd like for it to work again on Wayland.

The lack of logs is also weird, makes troubleshooting really hard.

For reference here is my wezterm config

gotlougit avatar Dec 12 '23 16:12 gotlougit

Hi same issue,

Please find 2 log files here gotten starting Wezterm from Konsole with "WEZTERM_LOG=debug wezterm "

2794 : started 2853 : not started

wezterm-gui-log-2794.txt wezterm-gui-log-2853.txt

The Wezterm icon pops in the task bar, I can close it from the task bar... but the window does not appear.

I'm running an up to date Archlinux, KDE Plasma under Wayland.

Hope this helps.

Regards.

Temet79 avatar Feb 04 '24 13:02 Temet79

Hello, I'm also having this issue, on Archlinux, KDE, Wayland as well. Here's the result of WEZTERM_LOG=debug wezterm (when wezterm fails to launch): wezterm_log.txt

Edit: On my computer with Fedora, Wayland, KDE it works flawlessly.

starmatt avatar Feb 17 '24 01:02 starmatt

I'm also running into this issue on hyprland! In my case, wezterm won't start at all.

Je12emy avatar Mar 01 '24 02:03 Je12emy

I'm also running into this issue on hyprland! In my case, wezterm won't start at all.

You were able to find the cause of the problem, literally yesterday, after rebooting, it stopped starting from keyboard shortcuts (I fixed it), and after the next reboot it stopped starting at all, and when starting from the terminal, it started complaining about the installed theme.

Kustikk avatar Mar 01 '24 13:03 Kustikk

stopped working for me yesterday

Revirae avatar Mar 05 '24 15:03 Revirae

I looks like the issue was solved for me with the upgrade to KDE 6 on Arch.

Temet79 avatar Mar 06 '24 20:03 Temet79

It seems the issue is fixed for me too after updating to Plasma 6 !

starmatt avatar Mar 07 '24 13:03 starmatt

I started having this issue yesterday using Hyprland on Void Linux. I really don't want to switch terminals. I really like Wezterm. I'll try the DEBUG flags and see if I can fix it

JoshElias avatar Mar 20 '24 12:03 JoshElias

Yep happening for me on Hyprland. With or without a config. I use Arch btw.

Had to disable enable_wayland to "fix" it.

mbwilding avatar Mar 24 '24 07:03 mbwilding

Having the same issue, completely fails to even launch on Hyprland (Arch). As @mbwilding suggested, explicitly setting enable_wayland = false will get it to actually launch, but this is obviously just temporary workaround, and far from an ideal solution.

ForeverZer0 avatar Apr 17 '24 02:04 ForeverZer0

The same issue. config.enable_wayland = false help me. But on Hyprland is not optional.

RadekRojik avatar Apr 29 '24 19:04 RadekRojik

I have the same issue, but wondering if this is a Hyprland problem and not a wezterm one. It works if i use the keyboard shortcut on a floating window. Any tiled windows, and wezterm will start, but not appear on the screen.

If you do it on a floating window, the window will appear. Strange behaviour.

kragebein avatar May 04 '24 06:05 kragebein

Wow, that's really strange. I can confirm what @kragebein is describing. I'm on Hyprland (wayland) and when having a tiled window focused, then wezterm will not start. But if a floating window is focused, it will!

luiswirth avatar May 26 '24 14:05 luiswirth

Is this a duplicate of #5103?

raffaem avatar Jun 01 '24 07:06 raffaem

@raffaem For me, it most definetly is.

luiswirth avatar Jun 03 '24 07:06 luiswirth

@raffaem For me it was, as well. As soon as the fix for that issue was merged, I built it from source and the issue was resolved.

I can't speak for all distros, but I can confirm for Arch users that the wezterm-git package fixes the problem if the wezterm one hasn't been updated yet. This of course assumes that it is the same problem.

ForeverZer0 avatar Jun 03 '24 09:06 ForeverZer0

@raffaem For me it was, as well. As soon as the fix for that issue was merged, I built it from source and the issue was resolved.

I can't speak for all distros, but I can confirm for Arch users that the wezterm-git package fixes the problem if the wezterm one hasn't been updated yet. This of course assumes that it is the same problem.

But the wezterm-git package requires a very long time to compile every time you update the system and there is a change upstream.

raffaem avatar Jun 03 '24 12:06 raffaem