Crash when returning from Assembly View in nightly build #325

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

Originally created by @warnesj on 3/14/2026

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.3.2-dev Build d28e964e

Operating System (OS)

Linux

OS Version

Fedora 43

Additional system information

CPU: AMD Ryzen 9 5900X
Memory: 32GB
GPU: NVIDIA GeForce RTX 3070 Ti
Windowing System: Wayland
GNOME Version: 49
Linux Kernel: 6.19.6-200.fc43.x86_64
Screen Count: 2 (if it matters)

Printer

Elegoo Centauri Carbon 2

How to reproduce

Please note, I'm using the nightly AppImage build as a workaround to slicing issues described in https://github.com/OrcaSlicer/OrcaSlicer/issues/11698. When using the nightly image, to reproduce the problem:

  1. Start a new project.

  2. Add a Primative like a cube. (Though the issue also happens with STL's.)
    Image

  3. Clone the cube once (or more, up to you).
    Image

  4. Highlight all the cubes by holding shift and dragging a box around them all.

  5. Right-click on any of the highlighted cubes and select "Assemble".
    Image

  6. With the new assembly still highlight, click on the Assembly View option in the toolbar (farthest right icon).
    Image

  7. When in Assembly View, click on the "< Return" botton in the top-left of the Assembly View window.
    Image

OrcaSlicer crashes at this point. (At least for me?)

Actual results

When running the AppImage from the command line, here is the output, from launch-to-end.

Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
No such file or directory

(orca-slicer:219116): Gdk-WARNING **: 11:27:38.097: The program 'orca-slicer' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 65659 error_code 8 request_code 150 (GLX) minor_code 11)
  (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.)

The "Inconsistent value (1)..." lines show up as OrcaSlicer windows open. OrcaSlicer seems to behave fine even with those warnings. The Gdk-WARNING and BadMatch error happens right when I click on the "< Return" button in the Assembly View.

Expected results

What I'm expecting to happen is when I click on the "< Return" button in the Assembly View is that I would be returned back to the main project view that shows the build plate.

Project file & Debug log uploads

Project File: Cube Assembly.zip
Logs: debug_Sat_Mar_14_11_47_50_246138.log.zip

Checklist of files to include

  • Log file
  • Project file

Anything else?

What's interesting is I don't experience this problem with the current stable release (v2.3.1) of the AppImage. But I'm unable to use that version due to slicing issues (described in https://github.com/OrcaSlicer/OrcaSlicer/issues/11698).

*Originally created by @warnesj on 3/14/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2-dev Build d28e964e ### Operating System (OS) Linux ### OS Version Fedora 43 ### Additional system information **CPU:** AMD Ryzen 9 5900X **Memory:** 32GB **GPU:** NVIDIA GeForce RTX 3070 Ti **Windowing System:** Wayland **GNOME Version:** 49 **Linux Kernel:** 6.19.6-200.fc43.x86_64 **Screen Count:** 2 (if it matters) ### Printer Elegoo Centauri Carbon 2 ### How to reproduce Please note, I'm using the nightly AppImage build as a workaround to slicing issues described in https://github.com/OrcaSlicer/OrcaSlicer/issues/11698. When using the nightly image, to reproduce the problem: 1. Start a new project. 2. Add a Primative like a cube. (Though the issue also happens with STL's.) <img width="605" height="551" alt="Image" src="https://github.com/user-attachments/assets/ae5424d2-e2a7-4c43-ab0d-29381e8468df" /> 3. Clone the cube once (or more, up to you). <img width="605" height="551" alt="Image" src="https://github.com/user-attachments/assets/1b0a873c-0e3d-4dfb-825b-895e7d202777" /> 4. Highlight all the cubes by holding shift and dragging a box around them all. 5. Right-click on any of the highlighted cubes and select "Assemble". <img width="605" height="551" alt="Image" src="https://github.com/user-attachments/assets/f6d6114f-b565-47ae-867f-e4434d3ae59e" /> 6. With the new assembly still highlight, click on the Assembly View option in the toolbar (farthest right icon). <img width="482" height="165" alt="Image" src="https://github.com/user-attachments/assets/da6519ed-4504-439d-9e7c-dc2b65110a3f" /> 7. When in Assembly View, click on the "< Return" botton in the top-left of the Assembly View window. <img width="296" height="171" alt="Image" src="https://github.com/user-attachments/assets/c905c01a-606d-4341-a439-b27553a45f77" /> OrcaSlicer crashes at this point. (At least for me?) ### Actual results When running the AppImage from the command line, here is the output, from launch-to-end. ``` Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0 Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0 Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0 Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0 Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0 No such file or directory (orca-slicer:219116): Gdk-WARNING **: 11:27:38.097: The program 'orca-slicer' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 65659 error_code 8 request_code 150 (GLX) minor_code 11) (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.) ``` The "Inconsistent value (1)..." lines show up as OrcaSlicer windows open. OrcaSlicer seems to behave fine even with those warnings. The Gdk-WARNING and BadMatch error happens right when I click on the "< Return" button in the Assembly View. ### Expected results What I'm expecting to happen is when I click on the "< Return" button in the Assembly View is that I would be returned back to the main project view that shows the build plate. ### Project file & Debug log uploads Project File: [Cube Assembly.zip](https://github.com/user-attachments/files/25998063/Cube.Assembly.zip) Logs: [debug_Sat_Mar_14_11_47_50_246138.log.zip](https://github.com/user-attachments/files/25998064/debug_Sat_Mar_14_11_47_50_246138.log.zip) ### Checklist of files to include - [x] Log file - [x] Project file ### Anything else? What's interesting is I don't experience this problem with the current stable release (v2.3.1) of the AppImage. But I'm unable to use that version due to slicing issues (described in https://github.com/OrcaSlicer/OrcaSlicer/issues/11698).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OrcaSlicer#325