Protocol violation when launching in Hyprland #5067
Comments
|
I get the same error |
|
I am also seeing the same problem |
|
I am using the git version of Hyprland on NixOS with wezterm 20240203-110809-5046fc22 which is newest release and am not facing this issue, maybe it's a Hyprland issue that was fixed? Try upgrading your Hyprland to the git version if possible and see if that fixes it maybe |
|
@nonetrix in fact, the issue is only reproducible with the git Hyprland image, but it's fine with the latest release (at least this is what I am experiencing). |
|
Hi there, This is definitely a hyprland-caused issue. I have dissected the beginning of these issues start in the range of hyprwm/Hyprland@9a6956f...2841092. These are a large bundle of updates that attempt to bump wlroots. Furthermore, given that this is an update to the wlroot protocol, it would still be necessary to handle in wezterm. Since this is bleeding edge, this may only apply for a certain subset of users who have updated recently. For those interested hyprwm/Hyprland@af0c8e2 is the latest functional commit to hyprland that runs wezterm. |
|
@sjcobb2022 thank you for the careful investigation!
Does this mean that this is a Hyprland bug, or that these intentional changes broke Wezterm (but shouldn't be reversed)? |
|
I do not believe that is a bug (would have to look into it more tho). I believe that it is a legitimate wlroots spec update that causes the behaviour of wezterm to be considered incorrect. All my other apps (and proton-based games) work just fine. |
|
@sjcobb2022 Makes sense! And yes, I also see GTK-based apps (like Thunderbird or my ags widgets) working just fine. |
|
is there a work around for this? @MariaSolOs @sjcobb2022 |
|
@inudev3 revert hyprland to hyprwm/Hyprland@af0c8e2 |
|
the latest release(20240203-110809-5046fc22) works fine. |
Do you have the same setup I described? I just updated |
Setting |
After updating hypland-git yesterday, it was completely unable to start |
This is behind main, therefore is functional. |
|
Is this fixed in wezterm-nightly or not? Is it related to any of the other Hyprland related issues in wezterm? And does Hyprland need to make this fix or does wezterm need to make it? |
@Jackaed This is not fixed (as of 3 days ago when I tried it last). As mentioned here #5067 (comment), this is a wlroots spec update, meaning that this should be handled by wezterm. I have moved to alacritty for the time being, as this, alongside #5079 make wezterm essentially unusable for me. |
|
@Jackaed A recent nightly update seems to have fixed the issue on Fedora. My exact version is |
|
@Andyterrify doesn't seem to have fixed it on NixOS. Building wezterm from source, the issue persists, and I can only get wezterm to start with $WAYLAND_DISPLAY=1 to force it to use xwayland. |
|
Note that this could be due to the recent Hyprland releases, I'm only on v0.37.1 and Hyprland is on v0.38.1. Will let you know once the update hits nixpkgs-unstable. |
wayland or xwayland? also did you enable enable_wayland on config ? |
Also what hyprland version is necessary, as this is caused by a hyprland issue. |
|
Hyprland 0.38.1 |
|
same here running kitty on hyperland as wezterm fails to open. |
|
still not working in hyprland? |
|
Not for me unfortunately. |
|
seems to be working now I changed |
|
Can this be closed? Just have to wait on distros to package it or a release I assume |
|
Works for me too now (on nightly obviously). |
|
Doesn't yet work for me on Hyprland 0.39.1, but it may be that this is fixed by Hyprland 0.40.0. Will test when nixOS packages the new Hyprland version. |
|
Just use the flake |
|
Installing the nightly from the PPA on Hyprland 0.40, still crashing |
|
Same here, I'm still having issues with |
|
I am on Fedora 40 now, Hyprland 0.40.0, and wezterm
20240508_153238_f6fdfeb9. Unless the fedora upgrade changed something,
wezterm is now running again in Wayland mode. I can confirm disabling
enable_wayland it uses X11 and enabling enable_wayland wezterm now uses
Wayland.
…On Thu, 9 May 2024 at 00:19, Maria José Solano ***@***.***> wrote:
Same here, I'm still having issues with wezterm 20240508_151422_6b66b667
and hyprland 0.40.0-1.fc39.
—
Reply to this email directly, view it on GitHub
<#5067 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEVLI3DEFXWGGRDZL56GFO3ZBKXILAVCNFSM6AAAAABDXTDXDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRGY2TAOBQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Andrei Vasile
|
|
@Andyterrify interesting. I just updated to Fedora 40 to see if it would solve my issue, but it didn't work for me. I'm using Asahi though, so maybe the fix didn't make it there (?). This is the error I'm currently seeing: >> wezterm
19:20:24.686 WARN wezterm_gui::termwindow::resize > cannot resize window to match Some(RowsAndCols { rows: 22, cols: 50 }) because window_state is MAXIMIZED
xdg_surface@25: error 3: xdg_surface has never been configured
Protocol error 3 on object xdg_surface@25:
19:20:24.696 ERROR wezterm_gui > running message loop: Protocol error 3 on object xdg_surface@25: ; terminating |
|
Could also just be buggy Asahi drivers I guess, but I doubt it's the case if it was fine before. But I couldn't imagine they are exactly reliable sometimes |
|
I'll double check again tonight, in the past it did run once before
breaking. I'm using the version from the copr, did you build it yourself?
…On Thu, 9 May 2024, 03:35 fuggy, ***@***.***> wrote:
Could also just be buggy Asahi drivers I guess, but I doubt it's the case.
But I couldn't imagine they are exactly reliable sometimes
—
Reply to this email directly, view it on GitHub
<#5067 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEVLI3CMDQS6YK7TMUIABPTZBLOHPAVCNFSM6AAAAABDXTDXDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRHAZDEMRVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I can confirm that with wezterm 20240508_153238_f6fdfeb9 on fedora 40 and
hyprland 0.40.0 wezterm does work natively with Wayland in my machine
…On Thu, 9 May 2024, 18:19 Andrei Vasile, ***@***.***> wrote:
I'll double check again tonight, in the past it did run once before
breaking. I'm using the version from the copr, did you build it yourself?
On Thu, 9 May 2024, 03:35 fuggy, ***@***.***> wrote:
> Could also just be buggy Asahi drivers I guess, but I doubt it's the
> case. But I couldn't imagine they are exactly reliable sometimes
>
> —
> Reply to this email directly, view it on GitHub
> <#5067 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEVLI3CMDQS6YK7TMUIABPTZBLOHPAVCNFSM6AAAAABDXTDXDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRHAZDEMRVHE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
This is now fixed for me |
Same here. I will close this now. |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Hyprland
WezTerm version
20240221_075452_95581d86
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
When using the main image of Hyprland, wezterm crashes.
To Reproduce
bind = SUPER, T, exec, wezterminhyprland.confto launch wezterm.Configuration
No config
Expected Behavior
For wezterm and Hyprland to work nicely together <3
Logs
Here's the output I obtain when running
WAYLAND_DEBUG=1 weztermwithin Hyprland:Anything else?
I initially reported this issue in Hyprland (hyprwm/Hyprland#4806) but the maintainer said that this seems like a bug in wezterm.
The text was updated successfully, but these errors were encountered: