2.3.2 AppImage produces X Window System Error #24

Open
opened 2026-04-05 16:18:10 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @RB14060 on 4/2/2026

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.3.2

Operating System (OS)

Linux

OS Version

Ubuntu 24.04.4 LTS | KDE Plasma 5.27.12 Wayland

Additional system information

CPU: 11th Gen Intel® Core™ i9-11900H @ 2.50GHz
Memory: 64GB
GPU: Intel Integrated GPU / NVIDIA RTX 3050 Ti 4GB

Printer

Bambu Lab P1S

How to reproduce

  1. Attempt to launch the 2.3.2 AppImage

Actual results

Attempting to start the 2.3.2 AppImage on Ubuntu 24.04.4 LTS produces a crash after the splash screen. The splash screen will display for a few seconds then it will disappear and the entire program crashes. Program works perfectly on the 2.3.1 AppImage. Starting the AI via the Terminal produces the following error output:

$ ./OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.2.AppImage 
libEGL warning: pci id for fd 25: 10de:25a0, driver (null)

pci id for fd 28: 10de:25a0, driver (null)
pci id for fd 29: 10de:25a0, driver (null)
libEGL warning: egl: failed to create dri2 screen
pci id for fd 28: 10de:25a0, driver (null)
pci id for fd 29: 10de:25a0, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 29: 10de:25a0, driver (null)


(orca-slicer:3306635): Gdk-WARNING **: 13:12:43.067: The program 'orca-slicer' 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 509 error_code 2 request_code 149 (GLX) minor_code 3)
  (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.)

Expected results

Program should launch and function normally

Project file & Debug log uploads

Only one line logged:

[info] 2026-04-02 13:19:57.453840[Thread 0x00007eea134ee300]:gui mode, Current OrcaSlicer Version 2.3.2 build c724a3f5

Checklist of files to include

  • Log file
  • Project file

Anything else?

I redownloaded the file from the releases just to be sure the download wasn't corrupted, and the same thing reoccurred.

*Originally created by @RB14060 on 4/2/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2 ### Operating System (OS) Linux ### OS Version Ubuntu 24.04.4 LTS | KDE Plasma 5.27.12 Wayland ### Additional system information CPU: 11th Gen Intel® Core™ i9-11900H @ 2.50GHz Memory: 64GB GPU: Intel Integrated GPU / NVIDIA RTX 3050 Ti 4GB ### Printer Bambu Lab P1S ### How to reproduce 1. Attempt to launch the 2.3.2 AppImage ### Actual results Attempting to start the 2.3.2 AppImage on Ubuntu 24.04.4 LTS produces a crash after the splash screen. The splash screen will display for a few seconds then it will disappear and the entire program crashes. Program works perfectly on the 2.3.1 AppImage. Starting the AI via the Terminal produces the following error output: ``` $ ./OrcaSlicer_Linux_AppImage_Ubuntu2404_V2.3.2.AppImage libEGL warning: pci id for fd 25: 10de:25a0, driver (null) pci id for fd 28: 10de:25a0, driver (null) pci id for fd 29: 10de:25a0, driver (null) libEGL warning: egl: failed to create dri2 screen pci id for fd 28: 10de:25a0, driver (null) pci id for fd 29: 10de:25a0, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 29: 10de:25a0, driver (null) (orca-slicer:3306635): Gdk-WARNING **: 13:12:43.067: The program 'orca-slicer' 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 509 error_code 2 request_code 149 (GLX) minor_code 3) (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.) ``` ### Expected results Program should launch and function normally ### Project file & Debug log uploads Only one line logged: `[info] 2026-04-02 13:19:57.453840[Thread 0x00007eea134ee300]:gui mode, Current OrcaSlicer Version 2.3.2 build c724a3f5` ### Checklist of files to include - [x] Log file - [ ] Project file ### Anything else? I redownloaded the file from the releases just to be sure the download wasn't corrupted, and the same thing reoccurred.
MrUnknownDE added the bugbugbugbugbugbugbugbugbugbug labels 2026-04-05 16:18:11 +02:00
Sign in to join this conversation.
No Label bug bug bug bug bug bug bug bug bug bug
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OrcaSlicer#24