Description of problem: When trying to run Slic3r (1.1.7 installed for F21), Slic3r won't start and throw some subroutines errors. Version-Release number of selected component (if applicable): Slic3r 1.1.7 How reproducible: Run Slic3r at least once. At this point and in my case, it worked (at first). Then, run it again a few days later, Slic3r crashes with subroutine errors. Trying to remove slic3r conf folder (.Slic3r) didn't help. Steps to Reproduce: 1. Run slic3r 2. Close Slic3r 3. Run slic3r again Actual results: Subroutine e_per_mm3 redefined at /usr/share/perl5/vendor_perl/Slic3r/Extruder.pm line 22. Subroutine retract_speed_mm_min redefined at /usr/share/perl5/vendor_perl/Slic3r/Extruder.pm line 27. Subroutine extruded_volume redefined at /usr/share/perl5/vendor_perl/Slic3r/Extruder.pm line 42. Subroutine e_per_mm redefined at /usr/share/perl5/vendor_perl/Slic3r/Extruder.pm line 47. Subroutine apply_config redefined at /usr/share/perl5/vendor_perl/Slic3r/GCode/PlaceholderParser.pm line 33. Subroutine make_slices redefined at /usr/share/perl5/vendor_perl/Slic3r/Layer.pm line 44. You cannot overwrite a locally defined method (id) with an accessor at /usr/local/share/perl5/Method/Generate/Accessor.pm line 30. Compilation failed in require at /usr/share/perl5/vendor_perl/Slic3r.pm line 57. BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Slic3r.pm line 57. Compilation failed in require at /usr/bin/slic3r line 15. BEGIN failed--compilation aborted at /usr/bin/slic3r line 15.
Any chance you've compiled you'r own version of Slic3r and installed Perl modules (not just form RPM) and now you have all of this installed system wide?
s/you'r/your/
(In reply to Miro Hrončok from comment #1) > Any chance you've compiled you'r own version of Slic3r and installed Perl > modules (not just form RPM) and now you have all of this installed system > wide? Hmm... Strangely, you may be right, even though I remember clearly trying to compile (with success by the way) because I had this error ... I suppose then those perl modules are the ones breaking the systemwide installed package ?
I'm not sure about it, but that would definitively be possible.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.