Skip to content
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 rendering is broken in master #336069

Open
pshirshov opened this issue Aug 20, 2024 · 15 comments
Open

Wezterm rendering is broken in master #336069

pshirshov opened this issue Aug 20, 2024 · 15 comments
Labels
0.kind: bug 2.status: wait-for-upstream Waiting for upstream fix (or their other action). 9.needs: upstream fix

Comments

@pshirshov
Copy link
Contributor

pshirshov commented Aug 20, 2024

❯  nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.10.6, NixOS, 24.11 (Vicuna), 24.11.20240819.18c70e9`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/store/cb28mf5ha3929l7y9vlwswaz40r9b1yn-source`

Screenshot_20240820_151114

@liketechnik
Copy link
Member

liketechnik commented Aug 20, 2024

@pshirshov
Copy link
Contributor Author

Seems like the workaround doesn't work for me:

❯ wezterm
wp_linux_drm_syncobj_surface_v1#65: error 4: explicit sync is used, but no acquire point is set
17:09:59.440  ERROR  wezterm_gui > running message loop: error during event_q.dispatch protocol_error=Some(ProtocolError { code: 4, object_id: 65, object_interface: "wp_linux_drm_syncobj_surface_v1", message: "" }): Protocol error (os error 71); terminating
warning: queue 0x55f988a471c0 destroyed while proxies still attached:

@SuperSandro2000
Copy link
Member

Try disabling Wayland and fallback to xwayland.

I tried the latest version from master and that didn't fix this bug.

@taotien

This comment was marked as duplicate.

@zierf
Copy link

zierf commented Aug 22, 2024

@pshirshov Setting the frontend to WebGpu also causes my WezTerm to crash.

The workaround is to set the following in the ~/.wezterm.lua configuration.

front_end = "WebGpu",
enable_wayland = false,

Frontend WebGpu without disabling Wayland crashes even in my pinned version. I guess OpenGL was still the standard back then and it didn't have the above bug with font rendering.

@zierf
Copy link

zierf commented Aug 22, 2024

I posted a temporary workaround using WezTerm as Flake in WezTerm Issue #5990. Then it doesn't matter if front_end is not set, OpenGL or has been switched to WebGpu.

Credits go to davidsierradz for figuring this out. I just described it in a little more detail.

@knl
Copy link
Contributor

knl commented Aug 23, 2024

I have the same issue on aarch64-darwin, where no wayland is used.

However, enabling front_end = "WebGpu" fixes the issue.

@SuperSandro2000
Copy link
Member

For me this issue got fixed on nixos-unstable without any changes to Wezterm. Maybe a mesa/driver update?

@matthiasdotsh
Copy link
Contributor

For me this issue got fixed on nixos-unstable without any changes to Wezterm. Maybe a mesa/driver update?

For me wezterm is still broken using nixos-unstable (1355a0c).

@SuperSandro2000
Copy link
Member

Is hardware acceleration working for you in other applications? If not that is the issue.

@dpc
Copy link
Contributor

dpc commented Sep 17, 2024

I can play TF2 and other 3d games just fine, wezterm rendering still just squares, just tried current nixos-unstable.

@pshirshov
Copy link
Contributor Author

pshirshov commented Sep 19, 2024

For me the rendering is still broken w/o webgpu and wezterm just crashes w/wegbpu

@eeedean
Copy link
Contributor

eeedean commented Sep 20, 2024

For me on macOS it's broken like seen with OpenGL- or Software-Frontend but works with WebGpu.

Cannot get it to correctly display on my NixOS VirtualBox VM (x86_64-linux) with 3D accelleration activated and VMSVGA Graphics Controller.
Wont start with WebGpu und is rendering broken with OpenGL or Software.

It seems to be broken since Rust 1.80 upgrade:

  • using a58bc8a, it does work (still Rust 1.79)
  • with c3aa7b8 it broke (due to 1.80 upgrade)
  • after e572285 it builds again, but the display is broken

I took the two upper commits from Hydra and the last one is of course your fix-merge-commit, @SuperSandro2000.

Either something related broke inbetween or it is actually something around the Rust 1.80-Migration. Unfortunately however, I have no clue about Rust. 🐱

Thanks for your efforts, maintaining the package!

@nezia1
Copy link

nezia1 commented Sep 23, 2024

For me the rendering is still broken w/o webgpu and wezterm just crashes w/wegbpu

Do you have a Nvidia GPU? If so, Wezterm is currently broken with Nvidia using WebGL, which is really bad for us NixOS users as long as rendering is still broken with OpenGL... See wez/wezterm#6050

@pshirshov
Copy link
Contributor Author

Nope, AMD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug 2.status: wait-for-upstream Waiting for upstream fix (or their other action). 9.needs: upstream fix
Projects
None yet
Development

No branches or pull requests