$ 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 https://slic3r.org/
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) => shlomifAssignee: bugsquad => pkg-bugs
1.3.0 actually got released one and a half year ago... https://slic3r.org/releases/1.3.0/ 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 oldCC: (none) => rickURL: (none) => https://slic3r.org/Severity: normal => major
Please test upcoming slic3r-1.3.0-1.mga7 in Core/Updates_testing repo!
CC: (none) => geiger.david68210
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
Assigning to QA, Advisory: ======================== 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: ======================== slic3r-1.3.0-1.mga7.i586.rpm slic3r-1.3.0-1.mga7.x86_64.rpm Source RPM: ======================== slic3r-1.3.0-1.mga7.src.rpm
Assignee: pkg-bugs => qa-bugs
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_updateCC: (none) => tarazed25, sysadmin-bugs
Keywords: (none) => advisoryCC: (none) => tmb
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0208.html
Status: NEW => RESOLVEDResolution: (none) => FIXED