-
-
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
OrcaSlicer crashes on connecting to Klipper UI, and gets (almost) permanently corrupted - Linux, NixOS 24.11 #8243
Comments
I am facing the same issue when adding an OctoPrint/Klipper connectivity to OrcaSlicer. I did a bit debugging by compiling it with debug info enabled and I got this backtrace with
I'm getting this dump on Debian 12, however it did also crash in the appimage format and also in the docker container. Unfortunately the debuginfod mechanism didn't get me the source code. Maybe I'll dig deeper into that direction. So the issue is probably a bit tricky, if it's not happening directly inside this repo, and actually there's no call flow from the repo code to WebKit at all.. But perhaps it has set something incorrectly before, or perhaps we're facing a bug in WebKit itself? I also gave a shot to
to
My version is v2.2.0 aka 1088d0 running on Debian 12 (Bookworm) on x86_64. |
I observe the same issue. I think it is a duplicate of the #7210
This is actually a WebKitGtk problem as it can be reproduced with their test program MiniBrowser connecting to the Mainsail UI. |
Hi, For fix this issue have switch to flatpak. Best Regards |
I hope you're tugging on my strings here, but, there is no such thing as OrcaSlicer on Flathub, nor is there a Flatpak release in the releases section. You're the first contributor to take notice of this thread, where multiple people are running into a segmentation fault, and your solution is to switch to the Flatpak? First off, I'd like to ask, why the Flatpak? Is it the safest or most stable release? If so, why isn't the Wiki up to date to reference this? Have a great day 😄 P.S. Just installed OrcaSlicer through the Nightly flatpak release, and I can confirm that the interface with the printer works correctly! Thanks for the advice, but please make it clear next time that the Flatpak release is a recent addition and that it's part of the nightly builds, it was kind of difficult to locate without no other info 😅 |
I had something similar happen with the flatpak release last night. Not sure if it's exactly the same, but I switched my printer from CrealityPrint to Klipper after rooting, Orca crashed and since then only opens with a black screen before immediately crashing again. Eventually got it reinstalled and working again with some extra environment variables form #8373 |
What I find interesting is this doesn't seem to be an issue on X11 but does happen on Wayland. I'm currently using the env variables
So I have verified that v2.2.0 appimage & v2.3.0-beta (aur) works on x11 but doesn't render anything in the home ordevice tab with no fixes but I can use it. The moment I add or
I will update with more back from waylands side. |
Is there an existing issue for this problem?
OrcaSlicer Version
2.2.0
Operating System (OS)
Linux
OS Version
NixOS 24.11
Additional system information
Kernel: Linux 6.6.72
Uptime: 1 day, 11 hours, 20 mins
Packages: 3520 (nix-system), 2136 (nix-user), 5 (flatpak)
Shell: fish 3.7.1
Display (DELL 1907FPV): 1024x1280 @ 75 Hz in 19" [External]
Display (27E1QA): 2560x1440 @ 144 Hz (as 2048x1152) in 27" [External] *
DE: KDE Plasma
WM: KWin (Wayland)
WM Theme: Layan
Theme: Breeze (Layan) [Qt], Layan-Dark [GTK2/3/4]
Icons: Papirus-Dark [Qt], Papirus-Dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: GoogleDot-Black (24px)
Terminal: .konsole-wrappe
CPU: AMD Ryzen 5 7600X (12) @ 5.45 GHz
GPU: AMD Radeon RX 7900 XT [Discrete]
Memory: 11.51 GiB / 31.09 GiB (37%)
Swap: 1.41 GiB / 33.20 GiB (4%)
Disk (/): 268.85 GiB / 598.00 GiB (45%) - btrfs
Local IP (wlp10s0): 192.168.1.22/24
Locale: en_US.UTF-8
Printer
Neptune 4
How to reproduce
~/,config/OrcaSlicer
and~/.local/share/orca-slicer
are deleted or cleared.Actual results
A beautiful SEGFAULT appears if trying this through the terminal, oh the lovely landscape of C++!
Expected results
I would expect OrcaSlicer to allow me to send files to my printer.
Project file & Debug log uploads
OrcaSlicer Bug Report.zip
log.zip
Checklist of files to include
Anything else?
Here's a link to a demonstration / official video bug report for this issue.
The text was updated successfully, but these errors were encountered: