Wezterm crashing on main

[MariaSolOs]

Hyprland Version

System/Version info

<Paste the output of the command here>

Sorry but given that I cannot even open a terminal, I can’t check this :(
According to dnf list —installed I have hyprland-git.aarch64 version 0.35.0^39.git8c36136-1.fc39 from the solopasha:hyprland copr.

Bug or Regression?

Bug

Description

After updating Hyprland to the latest git release, I’m not able to open Wezterm anymore.

How to reproduce

1. Install Wezterm.
2. Add a keybind like bind = SUPER, T, exec, wezterm in hyprland.conf
3. Using the main branch, notice how the terminal won’t open.

Crash reports, logs, images, videos

Before crashing, all I can see from Wezterm is a notification saying “running message loop: Protocol error 3 on object xdg_surface@23: “

EDIT: Kitty is working fine. My issues were caused by a .bashrc misconfiguration. I've updated this description accordingly.

[MariaSolOs]

Hmm this looks like a duplicate of #4798?

[vaxerski]

no, it's not a duplicate. Post WAYLAND_DEBUG=1 logs of a crashing app.

[MariaSolOs]

Of course. Here's the log file from Wezterm:
wezterm.log

[vaxerski]

that's... odd. I am on latest and kitty definitely launches for me, and the surface there seems to have been configured...

[MariaSolOs]

I know, it's quite strange... It's not happening with the stable image, which gives me the following hyprctl systeminfo output:

Hyprland, built from branch HEAD at commit 84ab8d1 (props: bump ver to 0.35.0). Date: Mon Feb 5 01:59:02 2024 Tag: v0.35.0

flags: (if any)

System Information:
System name: Linux
Node name: prettygirl
Release: 6.6.3-413.asahi.fc39.aarch64+16k
Version: #1 SMP PREEMPT_DYNAMIC Sat Jan 27 17:19:54 UTC 2024

GPU information:

os-release: NAME="Fedora Linux Asahi Remix"
VERSION="39 (Thirty Nine)"
ID=fedora-asahi-remix
ID_LIKE=fedora
VERSION_ID=39
VERSION_CODENAME=""
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Linux Asahi Remix 39 (Thirty Nine)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora-asahi-remix:39"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedora-asahi-remix.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f39/system-administrators-guide/"
SUPPORT_URL="https://discussion.fedoraproject.org/c/neighbors/asahi/asahi-help/94"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=39
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=39

plugins:

Here's some more information that might help:

• Wezterm version: 20240221_075452_95581d86
• My hyprland.conf file

[vaxerski]

It's wezterm's fault.

Can you add wayland_debug kitty logs?

[MariaSolOs]

I will be adding the kitty logs in a bit, currently AFK.

For my own knowledge, why do you say it's wezterm's fault? @vaxerski

[vaxerski]

because the protocol error is raised because wezterm violated the protocol. It looks like it accidentally unmaps its surface and doesn't go through the map process before trying to use it.

edit: fwiw, wezterm crashes on wayland all the time. I believe this is the third time wezterm does something wrong in wl.

[MariaSolOs]

I see. I had never had issues with Wezterm until now :(

As promised, here are the kitty logs:
kitty.log

[vaxerski]

no errors here in the log

[MariaSolOs]

no errors here in the log

But kitty is still not opening.

[vaxerski]

yeah idk inside kitty it looks like it just doesn't want to, it closes out of its own will it seems. Anyways, it might be a misconfiguration? It works just fine on my end

[MariaSolOs]

@vaxerski Even with an empty kitty.conf I have this behaviour...

It seems like this isn't Hyprland's fault, and the last thing I want is to make you more busy than you already are, but do you have any tips on what I can do to diagnose the problem? Without a terminal emulator my Linux setup is quite useless. Wezterm-nightly and Hyprland 0.35.0 work fine, so I can stick with those versions for now, but I don't want to miss important fixes/features because of this.

[vaxerski]

I wish I knew what's up.

one thing I remember is when I once broke my kitty by setting it to an XD size that would make it crash on launch. IIRC it'd store the "last state" somewhere. But that doesn't seem like the case here.

Have you tried e.g. foot? if that launches?

[MariaSolOs]

I haven't tried foot yet (I'm not that desperate since I still have a working setup lol) but I'll try that.

I will continue investigating. In the meantime, I think that some related issues are being created (e.g. #4813). Since I have an environment where I can consistently reproduce the problem, feel free to let me know if you want me to try out stuff to ease your investigation.

Also I take advantage of the opportunity to say that I truly admire and appreciate your work <3

[vaxerski]

4813 is unrelated, it's about hyprland crashing not the apps. It's a separate issue, most likely on their end

thanks for the kind words :)

[sjcobb2022]

Would like to add that this only occurs after after 9a6956f...2841092 trying to update wlroots.

Most likely the updated spec caught wezterm's incorrect usage of wl.

Wezterm is undergoing a large wayland rewrite atm, lots of stuff still unimplemented. I believe that the core-issue is that the wayland seat has not been properly implemented yet for wezterm, which causes the surface to not be configured, which causes it to violate a wl protocol.

af0c8e2 is the latest commit to hyprland that runs wezterm.

[vaxerski]

is this still a thing? if it's just wez, it's not a hl issue

[MariaSolOs]

@vaxerski yeah we can close this and let wez/wezterm#5067 track the problem with wezterm.