SoftFever
Segfaults on Linux after connected to Mainsail/fluidd
Is there an existing issue for this problem?
- [X] I have searched the existing issues
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
Checklist of files to include
- [X] Log file
- [X] Project file
Anything else?
I've tested it with and without the plugin blob and stealthmode active/disabled. Same results.
Hi, I confirm this, Orca Slicer 2.2 RC (and maybe older versions) DISTRIB_ID=LinuxMint DISTRIB_RELEASE=22 DISTRIB_CODENAME=wilma DISTRIB_DESCRIPTION="Linux Mint 22 Wilma" Config : Xiaomi Laptop Kernel: 6.8.0-47-generic arch: x86_64 bits on quad core model: Intel Core i5-8250U & GeForce MX150 - 8 Gb Ram
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
works fine if I delete the bambu network plug in and only use bambu profiles but if I switch to any of my other profiles for klipper or duet machines it crashes
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 From what I'm seeing, the problem comes from the Linuxmint side. When I go to the connection settings and then click on browse, it doesn't find any device. In Zorin OS work fine
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 foung the dpkg.log here is everything I updated yesterday on my desktop it stopped after that
2024-10-24 17:08:56 startup archives unpack
2024-10-24 17:08:57 upgrade google-chrome-stable:amd64 130.0.6723.58-1 130.0.6723.69-1
2024-10-24 17:08:57 status half-configured google-chrome-stable:amd64 130.0.6723.58-1
2024-10-24 17:08:58 status unpacked google-chrome-stable:amd64 130.0.6723.58-1
2024-10-24 17:08:58 status half-installed google-chrome-stable:amd64 130.0.6723.58-1
2024-10-24 17:09:03 status triggers-pending gnome-menus:amd64 3.36.0-1ubuntu3
2024-10-24 17:09:03 status triggers-pending desktop-file-utils:amd64 0.26+mint3+victoria
2024-10-24 17:09:03 status triggers-pending mailcap:all 3.70+nmu1ubuntu1
2024-10-24 17:09:03 status triggers-pending man-db:amd64 2.10.2-1
2024-10-24 17:09:03 status unpacked google-chrome-stable:amd64 130.0.6723.69-1
2024-10-24 17:09:03 upgrade distro-info-data:all 0.52ubuntu0.7 0.52ubuntu0.8
2024-10-24 17:09:03 status half-configured distro-info-data:all 0.52ubuntu0.7
2024-10-24 17:09:03 status unpacked distro-info-data:all 0.52ubuntu0.7
2024-10-24 17:09:03 status half-installed distro-info-data:all 0.52ubuntu0.7
2024-10-24 17:09:03 status unpacked distro-info-data:all 0.52ubuntu0.8
2024-10-24 17:09:03 startup packages configure
2024-10-24 17:09:03 configure distro-info-data:all 0.52ubuntu0.8
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! *edit....so by adding host ip after running OS, the systems freezes up and crashes.Adding the hostname does not crash but device mng says cannot connect to moonraker
as long as I don't have a hostname or ip in the Json file it seams to work ok
@broncosis @darco415
Half solution on LinuxMint 22 updated to today.
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: sudo apt install libwebkitgtk-6.0-4 libwebkitgtk-6.0-dev
updating web kit to version 6 like you suggested seems to have done the trick with out the port number but still testing ok so no after some testing it still crashes adding the port number seems to help for now
@el-quique Thank you very much, your solution with the moonraker port works perfect for me. I never used the device tab anyway.
@el-quique Thanks! I've just downloaded the v2.2.0 release and i can confirm the issue is still there, but your solution works!
I can send gcode to the printer over the network using
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 https://github.com/mainsail-crew/mainsail/issues/1922 and I also tried the badwolf browser it mentions, and same crash happened as soon as mainsail is loaded.
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:
And as soon as I change the host to mainsail it crashes immediately.
https://github.com/mainsail-crew/mainsail/issues/1922
-- Reply to this email directly or view it on GitHub: https://github.com/SoftFever/OrcaSlicer/issues/7210#issuecomment-2447417476 You are receiving this because you were mentioned.
Message ID: @.***>
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.
OrcaSlicer 2.2.0
Strange behavior. If I add "files" to the host address, everything works fine until I enter the Dashboard or G-Codes Viewer.
Host: klipper.local/files
PD: Upon entering to G-Codes Viewer: (WebKitWebProcess:37098): WARNING **: 21:37:47.424: The GStreamer FDK AAC plugin is missing, AAC playback is unlikely to work.
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. Hopefully, this network drama can be fixed.
https://github.com/SoftFever/OrcaSlicer/issues/7392
Thank you @el-quique , that solved the problem. I am running Mint Cinnamon 21.3 with 2.2.0 official:
sudo nala install libwebkitgtk-6.0-4 libjavascriptcoregtk-6.0-1 ( the first package pulled the second )
[IP]:7125 and mDNS works trident01.home.arpa:7125
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. Changing to port 7125 seems to work for now
Same here, on Ubuntu 24 with Creality K1C. Tried with Orca 2.2.0 and 2.3.0dev, but with no luck. The chash happens both when trying fluidd on port 4408 or mainsail on port 4409. Works fine only if I point to Creality Print on port 80 instead 4408 or 4409.
When running Orcaslicer with debug level 5, i found the following log:
cat debug_Wed_Dec_04_02_29_38_202407.log.0 [error] 2024-12-04 02:29:40.166533[Thread 0x0000725ea4fdc480]:calc_exclude_triangles:Unable to create exclude triangles [warning] 2024-12-04 02:29:41.175920[Thread 0x0000725ea4fdc480]:02:29:41 AM: Warning: Error running JavaScript: Unsupported result type [warning] 2024-12-04 02:29:41.401315[Thread 0x0000725ea4fdc480]:02:29:41 AM: Warning: Error running JavaScript: Unsupported result type [warning] 2024-12-04 02:29:41.403917[Thread 0x0000725ea4fdc480]:02:29:41 AM: Warning: Error running JavaScript: Unsupported result type [warning] 2024-12-04 02:29:41.404852[Thread 0x0000725ea4fdc480]:02:29:41 AM: Warning: Error running JavaScript: Unsupported result type [error] 2024-12-04 02:29:42.760406[Thread 0x0000725ea4fdc480]:calc_exclude_triangles:Unable to create exclude triangles
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" In PrusaSlice the same problem.
(orca-slicer:108111): GLib-GObject-WARNING **: 21:16:53.428: invalid cast from 'wxPizza' to 'GtkCellLayout'
(orca-slicer:108111): Gtk-CRITICAL **: 21:16:53.428: gtk_cell_layout_get_cells: assertion 'GTK_IS_CELL_LAYOUT (cell_layout)' failed
ERROR: WebKit encountered an internal error. This is a WebKit bug.
./Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(562) : internallyFailedLoadTimerFired
Segmentation fault (core dumped)
I think it will be useful to clarify: I have qidi q1 pro (fluidd)
I'm having this issue too.
I can connect, upload files, and start prints if I set "print_host" to "
I'm running
- Orca Slicer 2.2.0
- Nixos 24.11 release
- Hyprland 0.45.2
- Linux Kernel 6.12.1
- fluidd 1.31.1
- Moonraker v0.9.3-3-gccfe32f2
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.
