TrenchBroom 2024.1 (compiled from master branch)
Fedora 39 with kernel 6.8.6
Gnome 45 Wayland session
AMD Ryzen 5 7530U with Radeon graphics
Expected Behavior
Creating or loading a map file allows the user to edit the file in TrenchBroom instead of causing a crash / core dump.
Steps to Reproduce
Launch TrenchBroom from within a Wayland session and attempt to create a new map file or load an existing map file. TrenchBroom will crash with a core dump and a note about failing to initialize glew in the logs.
Alternatively, launch TrenchBroom with the environment variable QT_QPA_PLATFORM=xcb and see that it does not crash, but instead runs fine loading / creating any file from within XWayland.
The above is from the generated crash log.
It seems that TrenchBroom is unable to find an appropriate renderer when running under a Wayland session. Perhaps forcing it to use xcb in the meantime could be enough?
Unfortunately realizing now after I've already posted this that I've essentially created a duplicate issue of #3326. apologies. My search-fu was lacking.
System Information
TrenchBroom 2024.1 (compiled from master branch) Fedora 39 with kernel 6.8.6 Gnome 45 Wayland session AMD Ryzen 5 7530U with Radeon graphics
Expected Behavior
Creating or loading a map file allows the user to edit the file in TrenchBroom instead of causing a crash / core dump.
Steps to Reproduce
Launch TrenchBroom from within a Wayland session and attempt to create a new map file or load an existing map file. TrenchBroom will crash with a core dump and a note about failing to initialize glew in the logs.
Alternatively, launch TrenchBroom with the environment variable
QT_QPA_PLATFORM=xcb
and see that it does not crash, but instead runs fine loading / creating any file from within XWayland.Crash Info
The above is from the generated crash log. It seems that TrenchBroom is unable to find an appropriate renderer when running under a Wayland session. Perhaps forcing it to use xcb in the meantime could be enough?
Unfortunately realizing now after I've already posted this that I've essentially created a duplicate issue of #3326. apologies. My search-fu was lacking.