Bug 25473 - slic3r segmentation fault, and it is old
Summary: slic3r segmentation fault, and it is old
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: https://slic3r.org/
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Reported: 2019-09-25 20:47 CEST by Morgan Leijström
Modified: 2019-11-19 22:18 CET (History)
6 users (show)

See Also:
Source RPM: slic3r-1.2.9-10.mga7.src.rpm
Status comment:


Description Morgan Leijström 2019-09-25 20:47:37 CEST
$ slic3r
Gtk-Message: 20:36:35.033: Failed to load module "canberra-gtk-module"
Segmenteringsfel (minnesutskrift skapad)

On an fresh and updated install mga7 64bit Plasma, on machine i7-3770, Nvidia GTX760 (GK104) using proprietary driver GeForce 420 and later.

Installing package lib64canberra-gtk0 gets rid of the Gtk-Message, but not the segfault.

And, now version 1.3.0 is released
Comment 1 Lewis Smith 2019-09-26 11:13:12 CEST
See also https://bugs.mageia.org/show_bug.cgi?id=531#c12

Is the GTK warning important? Often such messages are not. If it is, should lib[64]canberra-gtk0 be a dependency of slic3r?

slic3r has no maintainer, so assigning this globally. Update the package?
CC'ing Shlomi because you are down for slic3r-experimental & slic3r-stable .

CC: (none) => shlomif
Assignee: bugsquad => pkg-bugs

Comment 2 Morgan Leijström 2019-11-15 00:19:27 CET
1.3.0 actually got released one and a half year ago...
Some of bugfixes and many improvements.
And as our current do not work at all...

I note a bold statement at https://slic3r.org/ :
"Dependencies? Nah.
Slic3r is super-easy to run: download, double click and enjoy. No dependencies needed. Hassle-free. For MacOS X, Windows, Linux. "

Just tested Appimage of latest development 1.3.1: build https://dl.slic3r.org/dev/linux/Slic3r-1.3.1-dev-4f5b935-x86_64.AppImage
from page https://dl.slic3r.org/dev/linux/
It launches cleanly and look very nice. (mga7-64, Plasma, Nvidia driver)
Sliced an object fetched from thingiverse, and verified the output OK at https://ncviewer.com/

Rick, i see you packaged 1.2.9

I dont know how to judge if 1.3.0 or 1.3.1 is best
Or not bother, drop slic3r from cauldron, and use Appimage instead?

Summary: slic3r segmentation fault => slic3r segmentation fault, and it is old
CC: (none) => rick
URL: (none) => https://slic3r.org/
Severity: normal => major

Comment 3 David GEIGER 2019-11-15 08:44:32 CET
Please test upcoming slic3r-1.3.0-1.mga7 in Core/Updates_testing repo!

CC: (none) => geiger.david68210

Comment 4 Morgan Leijström 2019-11-15 15:55:21 CET
Thank you David :)

Uninstalled 1.2.9, selected 1.3.0 which brought three dependencies; installing:

- perl-local-lib-2.0.24-2.mga7.noarch
- perl-Net-Bonjour-0.960.0-9.mga7.noarch
- perl-Net-DNS-1.200.0-1.mga7.noarch
- slic3r-1.3.0-1.mga7.x86_64

It launches and look very nice. (mga7-64, Plasma, Nvidia driver)
Sliced an object fetched from thingiverse, and verified the output OK at https://ncviewer.com/  And close the program.

Only output in terminal from where i launched it is a few lines of 
** (slic3r:30227): WARNING **: 15:46:21.499: invalid source position for vertical gradient
Not sure what that is about, but it do shading on the opbject for nice 3D visual effect.

Whiteboard: (none) => MGA7-64-OK

Comment 5 David GEIGER 2019-11-15 17:27:10 CET
Assigning to QA,


Our current slic3r package is a quite old (2015-06-17) and also it segfault using a proprietary nvidia driver. So this update fixes this issue updating to the latest maintained upstream release.


Packages in 7/core/updates_testing:

Source RPM: 

Assignee: pkg-bugs => qa-bugs

Comment 6 Len Lawrence 2019-11-16 09:18:36 CET
Mageia7, x86_64
Proprietary nvidia graphics - GeForce GTX970.
Installation of lib64canberra-gtk0 is part of the initial system setup here.

Installed slic3r and its attendant packages.
Invoked slic3r from the command line to reproduce the segfault.

Updated slic3r and two python packages.
No 3D printer here so all that could be tested was the gui.
That looks functional.  Tinkering with the buttons resulted in a fullscreen projection of a printing matrix (I think).

I defer to Morgan in comment 4 for the detailed test.

Good for 64-bits.  Validating on the basis of the advisory in comment 5.

Keywords: (none) => validated_update
CC: (none) => tarazed25, sysadmin-bugs

Thomas Backlund 2019-11-19 18:55:43 CET

Keywords: (none) => advisory
CC: (none) => tmb

Comment 7 Mageia Robot 2019-11-19 22:18:17 CET
An update for this issue has been pushed to the Mageia Updates repository.


Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.