-
-
Notifications
You must be signed in to change notification settings - Fork 950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[OrcaSlicer 2.1.1] Segfault when going to machine's g-code twice #6069
Comments
I believe this is a duplicate of #6020 |
This could be a duplicate, but my reproduction steps are closer to this one. |
I have the same issue |
For me last working stable version is 2.0.0, and not working 2.1.0 and newer |
Looks like it related with new Mesa due my friend use 2.1.1 with Debian 12 and main differences are - mesa, kernel, desktop environment kernel: my - 6.9.7 (git), friends - default Debian's 6.1.99 And that are all differences between our systems. |
Same here. 2.1.1 just seg faults shortly after opening. Tried older versions, but the result is the same, segfault right after opening. Version 2.0.0, 2.1.0 and 2.1.1 app images. Very sad today. :( |
I just checked with older Mesa and issue still exist, also I tried with Xorg and Wayland - still exist, and looks like one main difference between my system and my friends is DE or list of libraries. @SoftFever Where I can find debug symbols for latest builds? To get more information why it segfault in my case. I found that latest build with debug symbols was 2.0.0 but for me sqgfault starts from 2.1.0 |
I's working again for me after updating to Plasma 6.1.3 and Mesa. AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.6, DRM 3.57, 6.9.9-200.fc40.x86_64) |
Orca bot: this issue is stale because it has been open for 90 days with no activity. |
Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale. |
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.1
Operating System (OS)
Linux
OS Version
Ubuntu 23.10
Additional system information
Intel Core i5-8250U 64 / RAM 16 GiB / Intel UHD Graphics 620
Printer
Personalized version of Ender 3
How to reproduce
Actual results
the app crashes, segmentation fault in console logs
Expected results
I should be able to visualize and edit printer's G-code
Project file & Debug log uploads
Untitled.zip
Checklist of files to include
Anything else?
The text was updated successfully, but these errors were encountered: