-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Crashing on Linux. Again. Old fix no longer works. #7099
Comments
For me OrcaSlicer also stopped working today. Opens up, worsk for like 5seconds then hangs and closes. Console says segmentation fault. Worked fine just few hours earlier till the system auto update kicked in. 2.2.0-rc from AppImage. Did a rollback and we are back to normal. Please let me know what could I provide.
|
Same issue on Arch Linux, I am 99% sure an nvidia GPU causes the issue as on my other device with an AMD GPU, there are no issues |
Yeah it's something to do with the Nvidia GPU and the Webkit that Orca uses, since the previous fix had you installing a specific webkit and forcing Orca to use it. Super frustrating as it has been an issue for a while now(#5171, #1841, #3479) with no movement on an official fix. |
I will add that downgrading to 2.1.1 seems to still work with the linked WebKit fix. |
I am using the 2.1.1 official version, and I have to do the linked Webkit fix:
I'm on Pop!_OS 22.04 LTS x86_64 I think it started happening with the latest version of the nvidia drivers: nvidia-driver-560 |
Still happens on 2.2.2, but the EGL fix is usable. |
This was working for a while, but for some reason does not work anymore. Here is the errors I get when I run it from the terminal:
|
i have the same issue. i have mxlinux (debian 11) libjavascriptcoregtk-4.0-18_2.44.2-1~deb11u1_amd64.deb libwebkit2gtk-4.0-37_2.44.2-1~deb11u1_amd64.deb probably package libwebkit2gtk-4.0-37_2.46.3 is incompatible with orcaslicer appimage. |
Please try if flatpak from #3949 (comment) fixes the issue |
@anarsoul It does not. |
I can't seem to find the "2.2.2" version, although I did try this with 2.2.0 and 2.1.1, with all of them crashing instantly or after clicking a few buttons. Where is the 2.2.2 version? Although, 1.9.0 is usable (at the least) with the following environment variables:
|
https://github.com/SoftFever/OrcaSlicer/releases/tag/v2.2.0 |
That's 2.2.0, not 2.2.2 |
So this is a bit of a workaround but I just got a Saturn 4 Ultra and I needed to print some stuff for an HVAC/Ventilation setup so I can start printing ASAP and I got absolutely fed up with the constant issues that OrcaSlicer has on anything other than Ubuntu and brute forced my way into finding a way to get Orcaslicer to run reliably on my Fedora desktop. Theoretically this should work on any distro, including incompatible versions of Ubuntu, since it uses Distrobox to create a Ubuntu 22.04 terminal environment with known compatibility and known working dependencies and runs a compiled version from there. With Environment Variables I was able to get OrcaSlicer 60% working with occasional crashes and with some things that just didn't work like viewing the devices tab. The way I've now done it now has no crashes(so far) and everything works the way it's supposed to. ONLY slight issue is that I've noticed that viewing things in 3D isn't as smooth, so if you move it around it feels like low FPS. But it doesn't crash and slices perfectly so I'll take the win. I wrote a tutorial on Reddit here explaining the process. Forgive the crudeness, I was working on a lack of sleep and months of built up frustration at constantly fighting with Orcaslicer for a semblance of stability, and I'm mostly self taught so admittedly I'm not an expert. |
@trebory6 Following your procedure, running
...
|
The error fatal: unknown style 'zdiff3' given for 'merge.conflictstyle' typically occurs when the merge.conflictstyle=zdiff3 configuration option is set in Git, but the version of Git being used does not support the zdiff3 merge style. The zdiff3 merge style was introduced in Git 2.39, so using an older version of Git (pre-2.39) can lead to this error. If all else fails, you can delete the distrobox, delete the git clone, and try again. That's the good thing about Distrobox is that it's contained, so every time it's a fresh slate. I'm running git version 2.34.1 within the Ubuntu 22.04 container. Make sure you're running the right version by running this command while inside your Ubuntu distrobox:
|
It doesn't work on Ubuntu-Studio 24.04 either. Same crash even with the special Ubuntu version of the .AppImage. |
I will say that the tutorial I linked is confirmed, at least on my own personal end, to work with the Ubuntu 22.04 Distrobox terminal environment. Haven't tested it on anything other than my Linux system, but I can't see why it wouldn't work for other distros. |
I will give it at try when I have time. |
I mean, theoretically the workaround I linked to should work indefinitely since it's technically Ubuntu 22.04 being run inside a terminal container. You can update your OS all you want, but the container will remain version 22.04. And trust, me I know. Orcaslicer's linux support definitely needs improvement, but I am of the "Fine, I'll do it myself" mentality. |
Nope, it does not work on the version. You need to update git first, using the following commands: sudo apt-get install software-properties-common
sudo add-apt-repository ppa:git-core/ppa -y
sudo apt-get update # this will update git if you already have it. Install git if you don't already |
Can confirm it works, but it is terribly slow. This is because distrobox by default does not have access to your GPU. Now for me, if I try to add my gpu to distrobox (the way it is supposed to be added), it fails to do so. Even if it could, I fear that due to nvidia orca-slicer would crash again |
My problems are only related to network issues. Without adding the Hostname or IP for my physical printer, the slicer does not crash. When I add a remote connection, it crashes within 5 seconds. |
@stfngnsch try add a port to the hostname or IP |
Thank you very much, this kinda works. 7125 is the port for moonraker. Now I can slice and upload without crashing. But I can not access to moonrakers front end. This solution was already presented here: |
Is there an existing issue for this problem?
OrcaSlicer Version
2.2.0 Beta
Operating System (OS)
Linux
OS Version
Nobara Linux 40 (KDE Plasma) x86_64
Additional system information
Kernel: 6.11.3-200.fsync.fc40.x86_64
Uptime: 4 hours, 23 mins
Packages: 3286 (rpm), 55 (flatpak)
Shell: bash 5.2.26
Resolution: 2560x1440
DE: Plasma 6.2.0
WM: kwin
CPU: AMD Ryzen 5 5600X (12) @ 4.651GHz
GPU: NVIDIA GeForce RTX 4070 SUPER
Memory: 32009MiB
Printer
Elegoo Neptune 3 Pro
How to reproduce
Trying to open v2.2.0 Beta on Linux after recent package updates results in immediate crash of Orca Slicer.
Actual results
Trying to open v2.2.0 Beta on Linux after recent package updates results in immediate crash of Orca Slicer.
Expected results
Open and use Orca Slicer without issue.
Project file & Debug log uploads
Ultimate Drybox.zip
debug_Sun_Oct_13_15_.zip
Checklist of files to include
Anything else?
So originally the steps in this reddit post worked to fix the issue. At some point recently it no long works and now crashes as it did before.
Log File consists of the following:
[error] 2024-10-13 15:37:06.440864[Thread 0x00007ffb62ef1700]:calc_exclude_triangles:Unable to create exclude triangles
[warning] 2024-10-13 15:37:06.686551[Thread 0x00007ffb62ef1700]:03:37:06 PM: Warning: Error running JavaScript: Unsupported result type
[warning] 2024-10-13 15:37:06.692066[Thread 0x00007ffb62ef1700]:03:37:06 PM: Warning: Error running JavaScript: Unsupported result type
[warning] 2024-10-13 15:37:06.692606[Thread 0x00007ffb62ef1700]:03:37:06 PM: Warning: Error running JavaScript: Unsupported result type
[warning] 2024-10-13 15:37:06.734383[Thread 0x00007ffb62ef1700]:03:37:06 PM: Warning: Error running JavaScript: Unsupported result type
[error] 2024-10-13 15:37:08.130639[Thread 0x00007ffb62ef1700]:calc_exclude_triangles:Unable to create exclude triangles
The text was updated successfully, but these errors were encountered: