-
-
Notifications
You must be signed in to change notification settings - Fork 747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wezterm not starting with wayland_enable=1 on Hyprland-git #5103
Comments
Same, is this a issue with Hyprland or Wezterm though? |
I opened an issue on Hyprland's github , it turns out apparently the problem is on wezterm's side . |
So which version of Hyprland should I downgrade to? Sorry |
maybe need wezterm support the new wlroots protocol |
on release version 36.0 it works fine |
Anything released on or before the 28th of February. |
same issue since yesterday, won't start even if |
The Hyprland commit that "broke" WezTerm was hyprwm/Hyprland@f4f3aa2. All it does is send an initial size to the application so that it wouldn't need to resize itself again later and cause visual artifacts on startup. WezTerm still runs for me if I open another terminal (e.g. kitty), make it float, then launch |
in my case it doesn't start from a floating terminal but when i added a rule to hyprland's config to float wezterm btw, I get this error |
This works for me
This does not work for me |
wezterm just doesn't work for me at all on hyprland even if I start it from another terminal. It just doesn't open |
My solution is to build Wezterm without Wayland support. |
Mine was to patch Hyprland to get rid of that commit: https://github.com/ErrorNoInternet/configuration.nix/blob/main/packages/hyprland/remove-size-predictions.patch |
Hm might look into that, I wonder how I could apply it to the NixOS flake though |
you can explicitly declare disabling wayland support in config though. |
Yep. I just forgot this setting. But thanks for your suggestion. |
I think there was some confusion, I was referring to the revert patch |
Hyprland 0.37 just hit arch extra, I assume this will hit a lot more users now. Thank you @ShadowS0ng for the workaround 🥳 |
Waiting for wez/wezterm#5103 to be resolved
Waiting for wez/wezterm#5103 to be resolved
Waiting for wez/wezterm#5103 to be resolved
Waiting for wez/wezterm#5103 to be resolved
Waiting for wez/wezterm#5103 to be resolved
Waiting for wez/wezterm#5103 to be resolved
Waiting for wez/wezterm#5103 to be resolved
Waiting for wez/wezterm#5103 to be resolved
I have added temporary patch in .wezterm.lua until it's resolved. if os.getenv("XDG_CURRENT_DESKTOP") == "Hyprland" then
config.enable_wayland = false
else
config.enable_wayland = true
end |
Workaround for Sway 1.9: |
This has been working flawlessly for me since I saw it a few weeks ago. Thanks for sharing, @khjorth ! |
is this fixed? i am on nightly build and still errors. |
If you're getting errors and/or wezterm immediately closes that's a different issue. This one (wezterm run normally but no window appears) has been fixed. |
@wez Would you consider a new release? This is affecting lots of users it seems. |
Wezterm isn't working for now on Hyprland. See wez/wezterm#5103 (comment)
can confirm. Doesn't start at all, even with floating window workaround. Running under hyprland 0.41 on Arch git version works tho |
this issue has been solved , but the latest release doesn't include the fix . you need to move to the git version |
The problem still persists on NixOS, so if anyone uses it, you have to wait for the nixpkgs update, or search for the git flakes :( |
the flake is here: github:wez/wezterm?dir=nix |
I'm trying to build it for the home-manager, but the error is still there, maybe you could give some advice? inputs = {
# Specify the source of Home Manager and Nixpkgs.
nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
home-manager = {
url = "github:nix-community/home-manager";
inputs.nixpkgs.follows = "nixpkgs";
};
ags.url = "github:Aylur/ags";
wezterm.url = "github:wez/wezterm?dir=nix";
};
outputs = { nixpkgs, home-manager, ... }@inputs:
let
system = "x86_64-linux";
pkgs = nixpkgs.legacyPackages.${system};
in {
homeConfigurations."savvy" = home-manager.lib.homeManagerConfiguration {
pkgs = import nixpkgs {inherit system; };
#Ags
extraSpecialArgs = {inherit inputs; };
modules = [ ./home.nix ];
};
}; |
Nevermind, cudos to this comment in wezterm repo: |
That post is better than anything I would be able to provide anyway :) |
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-git
v0.36.0-31-g328ab431
WezTerm version
20240226-174525-22424c32
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
wezterm doesn't launch on Hyprland-git version after a commit on hyprland which i think does a size hint
WAYLAND_DEBUG=1 output:
To Reproduce
install hyprland git version and run wezterm
Configuration
config.warn_about_missing_glyphs = true
config.enable_wayland = true
config.audible_bell = "SystemBeep"
-- config.prefer_egl = true
config.enable_scroll_bar = true
config.initial_cols = 103
config.front_end = "OpenGL"
config.initial_rows = 29
-- config.window_background_opacity = 0.8
config.line_height = 1.1
-- config.cell_width = 1.1
config.hide_tab_bar_if_only_one_tab = true
config.xcursor_theme = "Bibata-Modern-Classic"
config.xcursor_size = 22
config.default_cursor_style = "BlinkingBlock"
config.cursor_blink_rate = 800
Expected Behavior
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: