Crashes on Wayland with nvidia driver 560.35.03 #3342
Comments
Wayland with Vulkan |
Wayland with OpenGL |
XWayland with Vulkan |
XWayland with OpenGL |
|
Downgrading the driver to 555.58.02 gets XWayland working - vulkan falls back to opengl, but opengl starts fine. It is probably because it seems to fall back to software rendering: |
|
cc @BlockoS |
|
I believe that there are two issues here in summary:
As to whether Vulkan via XWayland was ever working, I am not sure. I cannot test it anymore unfortunately as I cannot downgrade beyond 555 driver due to nvidia kernel module not building against 6.10 kernel. |
|
Should I report this to nvidia in parallel? |
Yes. |
Done: |
|
I ran the test case with |
|
I'm still on this driver, but haven't updated bgfx in a while. I fixed the Wayland support recently in bgfx. When I'm home, I'll update bgfx, and test again. However, for me, everthing was working fine under this driver (except Vulkan + XWayland being extremely slow, but that's a driver issue). |
|
Thanks for the wayland fixes! When I originally fixed them up so that something is actually rendered, I was not really sure what I was doing. Apologies for causing work. In my defense, it used to work good enough until the explicit sync changes arrived.
As this works (or used to work last time I tested) on AMD open drivers, it is entirely possible that this behaviour is at least partially caused by issues with the nvidia driver. From the egl-wayland issue:
|
Updated log of Wayland with Vulkan |
Updated log of Wayland with GL |
Updated log of XWayland with GL |
All of my recent work should have removed the |
|
I will double check later just to be sure. But I did run |
|
Ok something is off, I need to investigate further: |
|
Looks like the version shown in the console does not reflect the actual commit but needs to be bumped manually. My tree has only one difference against git master: $ git diff
diff --git a/makefile b/makefile
index fbf3b6a88..73f8245f4 100644
--- a/makefile
+++ b/makefile
@@ -98,7 +98,7 @@ wasm-release: .build/projects/gmake-wasm ## Build - Emscripten Release
wasm: wasm-debug wasm-release ## Build - Emscripten Debug and Release
.build/projects/gmake-linux-gcc:
- $(GENIE) --with-tools --with-combined-examples --with-shared-lib --gcc=linux-gcc gmake
+ $(GENIE) --with-tools --with-combined-examples --with-shared-lib --with-sdl --gcc=linux-gcc gmake
linux-gcc-debug64: .build/projects/gmake-linux-gcc ## Build - Linux GCC x64 Debug
$(MAKE) -R -C .build/projects/gmake-linux-gcc config=debug64
linux-gcc-release64: .build/projects/gmake-linux-gcc ## Build - Linux GCC x64 ReleaseI recompiled everything using
Maybe my system is broken somehow or the RPM Fusion drivers do something weird. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
On Fedora 40 x86_64 with latest nvidia driver and egl-wayland from updates testing, attempting to start examples under wayland crashes regardless of the renderer or the SDL videodriver.
To Reproduce
Steps to reproduce the behavior:
--with-sdl --with-waylandadded to the makefilecd examples/runtime../../.build/linux64_gcc/bin/examplesDebugExpected behavior
Examples start as normal
Additional context
Changing
SDL_VIDEODRIVERbetweenx11andwayland, or renderer with--glor--vulkanonly changes the errors. Defining__NV_DISABLE_EXPLICIT_SYNC=1allows both Vulkan and OpenGL renderers to work with wayland videodriver, but not with x11. Native Xorg session works with x11 videodriver (but not with wayland, obviously).The text was updated successfully, but these errors were encountered: