Since upgrade to kernel 6.10.10 or 6.10.11 and other packages updated at the same time slic3r has a distorted display when first opened. Resizing the window, even a tiny amount, restores the display properly. When opening any stl file for use to create the gcode that image is no longer manageable. The image cannot be selected with the mouse and functions that depend upon having the image selected are not usable. This includes scaling, cutting, creating multiple copies, rearranging on the printer deck, rotating, etc. Reproducible: Always Steps to Reproduce: 1.open slic3r and attempt to use if to create gcode for use with a 3d printer. 2. 3. Actual Results: images, once loaded into slicer cannot be manipulated in any way Expected Results: The image displayed should be able to be selected then the functions for scaling, rotating, creating multiple copies, and rearranging on the bed for proper printing should all function as previously done. I am using fedora 40, kernel 6.10.11, Workstation and slic3r has been working well until the last few updates. I have also downloaded the slic3r code and compiled it locally but the locally compiled version works the same as that installed with the rpm file. dnf list installed slic3r gives this ."slic3r.x86_64 1.3.0-33.fc40 @fedora"
Created attachment 2050175 [details] The slic3r window when first opened This is the way the slic3r app opens up
Created attachment 2050176 [details] slic3r window after a slight size adjustment
Created attachment 2050177 [details] slic3r window after adding an stl file but without resizing the window
Created attachment 2050178 [details] same stl file opened and after resizing the window
Created attachment 2050179 [details] same stl file after clicking on the object After clicking on the object in slic3r it should be selected and turned green The functions on the tool bar that are greyed out should become active and there should be a right-click menu available. The object cannot be selected so cannot be manipulated in any way.
When you reboot your system, you should be able to select an older kernel. Doe that make slic3r work again as expected?
On fedora 40, when opening slic3r with any available kernel between 6.10.9 and 6.10.12 the reported error is seen. I installed a VM with f39 and fully upgraded it. On f39 slic3r works properly with all kernels including the latest, 6.10.12 It appears this regression appeared with the upgrade between fedora 39 and fedora 40. As such it seems that some supporting dependency may be a factor.
(In reply to Miro Hrončok from comment #6) > When you reboot your system, you should be able to select an older kernel. > Doe that make slic3r work again as expected? See comment 7
Note that on Fedora 41 Beta I find that slic3r again works in every apparent way EXCEPT the initial setup wizard when slic3r is newly installed and opened for the first time does not function. I was able to use the settings and configure it, but the wizard fails.
I suspect the failure of slic3r is because of the changes in python between fedora 39 and each fedora release since. Python 3.11 on fedora 39 is changed with upgrades to python 3.12 and 3.13. If slic3r is not actively maintained to remain current with python upgrades it would be expected to fail at some point.
Slic3r does not use Python.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. 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 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.