-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Not able to export directly to mounted devices #6758
Comments
Related to #4772 ? |
I am on Fedora 34 so I tried it with the 2.3.3 AppImage and could not reproduce it. It works either by clicking on "Export G-code" and browsing to the USB mount directory or by clicking on the SD/USB icon to the right of it which takes me directly to the mount directory. Either way I can save the g-code file and there is no crash. |
Great, gonna try the appimage (even thought I prefer the installed version through rpm or flathub). |
there is a update building for PrusaSlicer 2.3.3 with more permissions. I hope this fixes the issues. |
@Masterv98 Please report back when you where able to update so this ticket can be closed. |
YES, IT WORKS NOW!!!! THANK YOU GUYS SO MUCH!! |
@bubnikv this is solved |
Great, thanks! |
Version 2.3.3
OS: Fedora 34 Workstation (literally out of the box) (Linux)
Biqu B1 modded (og E3D V6) with modded marlin 2.0.9.1
Behavior
After slicing, when you go to export the Gcode, it opens a new window with a file explorer so you can export. Although it only shows your home directory, not any thumbstick or anything. If you select "other locations", the file explorer will crash. Even though I can access everything directly with the file explorer.
I've been exporting to a random folder to then move to my thumb drive. It's not a major bug, but it's annoying. I tried on the windows version (even though it takes longer to slice there because, windows....) the export directly to an external drive is much easier.
The text was updated successfully, but these errors were encountered: