-
-
Notifications
You must be signed in to change notification settings - Fork 956
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
Segfaults on Linux after connected to Mainsail/fluidd #7210
Comments
Idem in LinuxMint 22. |
Hi, I confirm this, Orca Slicer 2.2 RC (and maybe older versions) It seems to be a problem with the network plugin. I have to disable my eth network when switching from printers to avoid the segfault. Maybe due to a recent update to the BBL plugin, it was working right before. |
debug_Sat_Oct_26_11_26_02_55407.log.txt here is my most recent log similar behavior |
debug_Sat_Oct_26_03_10_16_36610.log.txt ok I was able to use my Duet profile fine but as soon as a chose to use my stealth changer which is klipper it crashed |
Problem HOST Conection |
well as I did updates yesterday that broke it there was a bunch of webkit packages updated I am trying to find a txt file to copy and paste 2024-10-24 17:08:56 startup archives unpack |
I just updated webkit on my LM22 just now hoping previous issues were addressed. Now on the RC, it flashes the home screen and it goes dark. Followed OP instructions and it worked, also device tab is working now???? Thxs Bro! |
@broncosis . Hello. You are using LM Debian Edition? or LM Cinnamon |
@el-quique Cinnamon |
as long as I don't have a hostname or ip in the Json file it seams to work ok |
In the host for the printer connection use: "ip or host":7125 7125 is the port for moonraker (control in moonraker.cfg file). You can upload gcode files to the printer, but we will not have them displayed in the device tab. It might be a good idea to install: |
ok I have been just exporting gcode and uploading it manually |
updating web kit to version 6 like you suggested seems to have done the trick with out the port number |
@el-quique |
@el-quique I can send gcode to the printer over the network using :7125 and OrcaSlicer works just fine. |
Thank you very much, this have made my day! |
I think that has to be a bug in webkit (or libwebkit2gtk) because I can put any valid url as the printer's host and it works perfectly well, as long as the url does not point to mainsail: And as soon as I change the host to mainsail it crashes immediately. I found this issue Side note: this also happens with BambuStudio and PrusaSlicer as well. |
Mine points at fluid which also crashes
Makes me kinda feel like the bug is in mainsail and fluid as it's the only thing that fails.
Get BlueMail for Android
…On Oct 30, 2024, 7:54 AM, at 7:54 AM, Noisyfox ***@***.***> wrote:
I think that has to be a bug in webkit (or libwebkit2gtk) because I can
put any valid url as the printer's host and it works perfectly well, as
long as the url does not point to mainsail:
![image](https://github.com/user-attachments/assets/fa4def80-f42a-45ce-a224-f2ee3e32ea19)
![image](https://github.com/user-attachments/assets/c15840ba-cc1a-455f-a942-386cee45918e)
And as soon as I change the host to mainsail it crashes immediately.
mainsail-crew/mainsail#1922
--
Reply to this email directly or view it on GitHub:
#7210 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
They might share similar designs that triggered this issue. |
Moved up to 2.2.0.4 release build and adding the Moonraker port 7125 to the address alleviates the SEGFAULT and allows the networking to function for sending files. However, this causes the Device tab to attempt to connect with Mainsail instead of Fluidd with a Mainsail info screen instead of the main Mainsail UI. |
I had similar issue with Cinnamon 21.3 and the solution is to avoid any network interaction, otherwise, the slicer gets into a crash loop, and fresh start with a few catches. I got 2.2.0 official running on Mint Cinnamon 21.3 but without network, Mainsail/browser is better than no slicer at all. |
Thank you @el-quique , that solved the problem.
|
Same thing on Ubuntu 24 Today the slicer just randomly decided to work. Then I realized that I for once started it before I turned on the printer. It still worked fine once the printer was started, could upload and stort jobs as usual, until i tried "reload" on the device screen. |
Same here, on Ubuntu 24 with Creality K1C. Tried with Orca 2.2.0 and 2.3.0dev, but with no luck. When running Orcaslicer with debug level 5, i found the following log: cat debug_Wed_Dec_04_02_29_38_202407.log.0 I get the same problem on PrusaSlicer 2.8.1 too. |
Today, I managed to get it working: i've done port forward (NAT) of the ports: 2222, 80, 9999, 5353, 4409, 4408 and 8080 on my firewall to access it outside my house. Then, I configurated OrcaSlicer to the external IP and external port and, strangely enough, Orcaslicer worked with both Fluid (port 4408) and mansail (port 4409). I hope this information can be helpful to solve the bug. |
Also crashes when connecting to Partially the functionality worked when installing the non-working prefix "device UI"
I think it will be useful to clarify: I have qidi q1 pro (fluidd) |
I'm having this issue too. I'm running
Due to the fact that I'm running nixos, the expected version of webkitgtk is included along with orca-slicer and this was recently fixed to be the most correct version a few days ago (before this, orca wouldn't even install via package or app image so I can't determine if the fluidd issue occurred before this update). I can probably find the relevant issue on the nixos page if it would help, but I don't think it's a webkitgtk issue. |
Just like isaac, im also on NixOS (Unstable) and have the exact same issue as well. |
I discovered this issue recently when I reloaded my system and went from KDE NEON on Ubuntu 22.04 to the latest KDE NEON on Ubuntu 24.04. I am fine until I enter the IP address of the printer (Ender 3 v2 on Klipper Raspberry Pi). As soon as I enter the IP, Orca crashes with a segment fault. I tried the latest nightly build, and the problem is there also. |
I encountered this on Ubuntu 24.04 with all possible images, including the daily build. I have a Voron configured and in the file And that stopped the crashing. So @el-quique's fix works. |
I'm having this problem both with flatpak and appImage install of nightly and latest versions. |
I'm encountering this with the flatPak and Appimage on Manjaro. |
Is there an existing issue for this problem?
OrcaSlicer Version
OrcaSlicer_Linux_Ubuntu2404_V2.2.0-rc
Operating System (OS)
Linux
OS Version
GNU/Linux Mint 22
Additional system information
AMD Ryzen 5600G, NVIDIA 1660 GPU.
Printer
Sovol SV06 and Rook MK1
How to reproduce
Backup and then delete ~/.config/OrcaSlicer dir;
Run orcaslicer and go thru the setup wizard;
Click the Connection icon next to the printer's name and setup "Hostname, IP or URL", hit OK;
Orcaslicer freezes and segfaults.
Go to ~/.config/OrcaSlicer/user/default/machine and edit the printer's .json config file by setting the "print_host" parameter to "".
Orcaslicer is working again!
Actual results
Orcaslicer freezes and segfaults.
Expected results
Orcaslicer should run normaly and gain access to my printer over the network inside de DEVICE tab.
Project file & Debug log uploads
Cube.3mf.zip
log.zip
Checklist of files to include
Anything else?
I've tested it with and without the plugin blob and stealthmode active/disabled. Same results.
The text was updated successfully, but these errors were encountered: