-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
Superslicer 2.4.58.2-3 crashes upon launch (Segmentation fault) #2938
Comments
I also have this exact same issue also with the appimage `❯ superslicer -loglevel 5 (process:10480): Gtk-CRITICAL **: 20:16:14.345: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (process:10480): Gtk-CRITICAL **: 20:16:14.345: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (process:10480): Gtk-CRITICAL **: 20:16:14.345: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (process:10502): Gtk-CRITICAL **: 20:16:25.085: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (process:10502): Gtk-CRITICAL **: 20:16:25.086: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (process:10502): Gtk-CRITICAL **: 20:16:25.086: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed |
I'm also experiencing the same issue on Garuda Linux (5.18.11-zen1-1-zen). `🧱] × superslicer -loglevel 5 [2022-07-14 19:17:26.801633] [0x00007f2389469d80] [debug] single instance: undefined. other params: superslicer;-loglevel;5 [2022-07-14 19:17:26.801637] [0x00007f2389469d80] [debug] full lock path: /home/midas/.config/SuperSlicer/cache/2431162533544861404.lock [2022-07-14 19:17:26.801644] [0x00007f2389469d80] [debug] Creating lockfile. [2022-07-14 19:17:26.801647] [0x00007f2389469d80] [info] Instance check: Another instance not found or single-instance not set. [2022-07-14 19:17:26.829338] [0x00007f2389469d80] [trace] System language detected (user locales and such): en_US |
I have the same issue since last night on Arch Linux. I rolled back the affected packages with the following command:
You can leave out kicad if you don't have it installed, of course. I also think that this is already fixed in the latest version of superslicer and would also be fixed in Arch and it derivatives when they upgrade superslicer to the latest version (2.4.58.3). |
it's the version from yesterday that is problematic? |
No, it's not because of superslicer (at least I think so). |
Yeah this definitely looks to me like an issue with SS not liking the new version of wxwidgets-gtk3 |
SS does indeed segfault after the arch updates, but the latest prusaslicer 2.5 appimage works just fine ... |
prusa updated many libraries for 2.5 (but not wxwidget), maybe it's why it still works. |
I tried rolling these back and had to delete the contents of both /usr/share/SuperSlicer/ui_layout/example/ and its counterpart in my .config directory. But this at least got me up and running for now. |
same on Fedora36 using SuperSlicer-ubuntu_18.04-2.4.58.3.AppImage. i don't appear to have anything 'wx' related installed (no wxwidgets, no wxgtk...) |
Same for me on EndeavourOS - if I delete directories resources/ui_layout/example and resources/ui_layout/default it starts fine and seems to work perfectly. |
same, arch |
Looks like SS on the arch repo finally updated today. Has anyone tried it?
…On Mon, Jul 18, 2022, 14:56 serproqnx ***@***.***> wrote:
same, arch
—
Reply to this email directly, view it on GitHub
<#2938 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGNBACBIOLD7AU6QHFWO2ELVUWSGPANCNFSM53TY5J7A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: sdooweloc ***@***.***> Date: 7/18/22 3:04 PM (GMT-05:00) To: supermerill/SuperSlicer ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [supermerill/SuperSlicer] Superslicer 2.4.58.2-3 crashes upon launch (Segmentation fault) (Issue #2938)
Looks like SS on the arch repo finally updated today. Has anyone tried it?
On Mon, Jul 18, 2022, 14:56 serproqnx ***@***.***> wrote:
same, arch
—
Reply to this email directly, view it on GitHub
<#2938 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGNBACBIOLD7AU6QHFWO2ELVUWSGPANCNFSM53TY5J7A>
.
You are receiving this because you commented.Message ID:
***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
just tried new version from arch repo ( |
prusa-slicer-2.4.2-6-x86_64 segfault on arch too |
fwiw PrusaSlicer-2.4.2+linux-x64-GTK3-202204251120.AppImage fine on fedora36 so looks like its affecting different distros differently. |
Same over here, Manjaro Linux. I am unable to rollback, though I did try. Definitely an issue with the new wx library. PrusaSlicer 2.5 works perfectly from app image. Interestingly the tar'ed version from releases right here will run, while the version from Arch fails with the seg fault everyone else has reported. |
prusa works now after last core updates just sudo pacman -Suy |
maybe it's related prusa3d@ec6192a |
|
@serproqnx can you try latest nightly? i merged the commit you linked. |
i've just tried this myself (Fedora36):
however, if i rename the ~/.config/SuperSlicer/ folder for a first-time run, then the log changes slightly:
Note that the second line changes from 'file exists' to 'Invalid cross-device link'. To my untrained eye, it looks like something going wrong with colors.ini update/creation and it having an effect on the GUI/Display initialisation process? edit: looking at the .../default/colors.ini from my preivously working --datadir path, i can see it's 712Bytes with 29 lines. |
same here on nightly, using gnome 42.3 and arch based |
rename from what? It wasn't created? |
rename to anything (or delete it); so when you start SuperSlicer, a new '~/.config/SuperSlicer/' folder will be created. |
rename and delete don't work. even tried with a fresh OS install and the same fault happens to SS |
I wasn't saying that would fix it, but in my post 5 hours ago with 2 different outputs; one was with an existing '~/.config/SuperSlicer/' folder, and the other was with that folder deleted/renamed (so next run of SuperSlicer would recreate them). what i was getting at was based on the original report/actual output of my computer, wxwidgets does not seem to be the case and is appears to be something around file creation/update/colors.ini. hopefully thats clearer :) @supermerill - your earlier commit build (257157) works for me - thanks!
|
Second run does not exhibit the same errors, so i think we're good?
|
more likely related to a change in the buildscript, they now build and static link prusa's patched wxWidgets |
i can confirm that "test for #2938" build does not segfault for me anymore on arch |
So not trying to be, "that guy" or anything, but when could we expect these nightly changes to be added to a main release? |
I'll try to resolve all the most glaring issue, to avoid creating multiple release per week. |
update: there is a big bug. I'll delay the release for a day or two to try to catch it. |
I'm glad you were able to track it down! Thank you for the work you do! |
This also fix #2936 |
What happened?
I'm using Arch Linux with the Linux 5.18.11 kernel.
Used to have the Superslicer version from the AUR installed. I just switched to the official one to update and ever since I can't get it to start, all it shows is "Segmentation Fault (core dumped)" if I launch it from the terminal.
I don't know what else I can tell you. On the AUR version all I did was set up my configuration. I renamed the ~/.config/SuperSlicer folder to check if that might have been the cause, but it segfaulted nonetheless.
Project file & How to reproduce
Steps I took:
1: Get Superslicer 2.4.58.2-3 from the official Arch Linux community repository.
2: Launch it from the terminal using
superslicer
.3: See segmentation fault error.
Version
2.4.58.2-3
Operating system
Arch Linux (Linux kernel 5.18.11)
Printer model
Not relevant
The text was updated successfully, but these errors were encountered: