Andrey Viktorov
Andrey Viktorov
Temporary solution: use `__NV_DISABLE_EXPLICIT_SYNC=1` env when running wezterm
Also the same commit seems to break webgpu frontend, and it also crashes on non-nvidia for me, with the same error and additional panic. Log from my nvidia machine with...
And here's log from my Intel iGPU machine with WebGpu enabled: wezterm-gui --config="front_end='WebGpu'" ``` ▲ ~ RUST_BACKTRACE=1 wezterm-gui --config "front_end='WebGpu'" wp_linux_drm_syncobj_surface_v1#53: error 4: explicit sync is used, but no acquire...
I don't know if this is related or not, but now wezterm also does not redraw sometimes until I move mouse cursor 🤔
> > I don't know if this is related or not, but now wezterm also does not redraw sometimes until I move mouse cursor 🤔 > > [@4ndv](https://github.com/4ndv) [@pyroraptor07](https://github.com/pyroraptor07) Don't...
> > Since the updated nightly last night, I am experiencing the same issue. Wezterm quits on boot. I have 2 150% scaled 4K screens on a Nvidia RTX 3080....
> Just updated my packages and wezterm works now. Not sure exactly which update fixed it though (since I didn't try it before the latest update as of writing). Even...
Same(-ish) issue for me Log ``` [@ciderapp/genten] Booting in production mode HELLOOOOOOO!)(#@!)@!(*@)!*@)!*)@! [@ciderapp/genten] Updated client options with new defaults [@ciderapp/genten] Using default hardware acceleration [@ciderapp/genten] Loaded module: cli [@ciderapp/genten] Loaded...
Still present for me
The issue is still present, no changes, same version