-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Prusa-Slicer Printables.com integration is broken #246261
Comments
I can reproduce this. Sadly th logging messages don't seem to be helpful and the last supported curl version doesn't easily build with the current curl derivation. Interestingly the API of libcurl should be backwards compatible. The issue isn't the lib version but the build flags that are used when prusa-slicer builds its vendors dependencies. Those are in the I'm not sure when and if I have time to debug this. :/ |
I can confirm that this still happens on 2.8.1 |
I tried to find out why by contacting another maintainer: flathub/com.prusa3d.PrusaSlicer#101 (comment) |
Seems to be curl related: flathub/com.prusa3d.PrusaSlicer#101 (comment) So we'd need to get Prusa slicer linked to curl 7 |
Describe the bug
The
prusa-slicer
package v2.6.0 does not correctly integrate with Printables. The printables.com integration fails with every single model; all downloads fail when attempting it and results in a 0kb file created onto my computer.Steps To Reproduce
Example: Fabric coasters model page
direct PS link:
prusaslicer://open?file=https%3A%2F%2Ffiles.printables.com%2Fmedia%2Fprints%2F230356%2Fstls%2F2096125_9cfc404b-0edb-4c30-a332-5ae014742d16%2Fmodular__004___x1x2.stl
Loading of a ZIP archive on path /home/novaviper/Downloads/fabric-coasters-model_files.zip has failed.
(orFailed to load model
if imported a model directly) and the model not opening up within the slicerExpected behavior
The slicer should just download the files/folders just fine with no error
Screenshots
What the buttons look like on Printables
The error
Additional context
In this issue, it maybe related to how the package maintainers have packaged the dependencies because a very similar issue occurred with the ArchLinux packaged version and it was deemed to be specific to the distro version of the program (and not the AppImage version). However I actually can't confirm this because I can't get the AppImage to run correctly on NixOS. I can get it to run with
appimage-run
but unfortunately can't get the desktop integration to work (running the desktop files it creates results in a "file not found" error).Notify maintainers
@Moredread
@tweber
Metadata
The text was updated successfully, but these errors were encountered: