Slade3 crashes on Linux when opening any graphics file

[Kzer-Za]

SLADE Version: (3.1.4.1) Operating System: (Linux)

Issue Details: The subject. At least it crashes with any of the files that I have. The output of the console is:

(slade:24080): Gdk-ERROR **: 19:42:10.592: The program 'slade' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 60185 error_code 2 request_code 154 (GLX) minor_code 24)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
zsh: trace trap (core dumped)  slade

The version of X Org server is 1.20.2-1.0 Kernel is 4.19.8-1 Video drivers are NVidia 340.107-7

[sirjuddington]

Are you using Wayland instead of X? I had a similar issue with Wayland (apparently wx3.0 opengl canvas doesn't like it, I think it's fixed in wx3.1)

[Kzer-Za]

Are you using Wayland instead of X?

No, I'm using X.

BTW, I updated Slade to 3.1.4.2 and now it gives a different error (it still doesn't open any graphics file):

(slade:9343): Gdk-ERROR **: 09:34:32.965: The program 'slade' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 91878 error_code 170 request_code 154 (GLX) minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
zsh: trace trap (core dumped)  slade

[sirjuddington]

I have no idea what it could be then unfortunately.

Edit: out of interest, what is the value of the gl_depth_buffer_size cvar for you? If it isn't 24, try setting it to that

[WilliamWeberBerrutti]

Hello, I have the same issue. Details below:

(slade:8802): Gdk-ERROR **: 11:10:07.577: The program 'slade' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
  (Details: serial 13128 error_code 170 request_code 154 (GLX) minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)

Operating System: Manjaro Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 4.19.88-1-MANJARO OS Type: 64-bit

Edit: How do I check the gl_depth_buffer_size variable?

Edit²: I think I've found a workaround: I was using NVidia proprietary drivers (video-nvidia-340xx), which caused this error. I changed to the open source one (video-linux) and I can finally open and edit graphic files inside Slade.