-
Notifications
You must be signed in to change notification settings - Fork 2k
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
2.9.0. Linux flatpack - No way to select second 'disk' #13862
Comments
|
Please search for existing issues before opening new ones. For example your issue sounds like its the same as either this #13844 or #13820 Both of which appear to be down to the way Flatpack works. You might want to try #13820 (comment) to see if it can resolve your problem. |
Thanks. 'Yet Another Permissions System' :-( |
@mw46d You can also use this AppImage from this relevant issue |
I'm also having problems with the Flatpak and running a post-processing script using Python. I have given all the necessary permissions, but it refuses to run my script. So, I'm just using the AppImage from the link above, and it runs fine now. Thanks to @probonopd for making this possible! |
closed as duplicate of #13820 |
Description of the bug
I have an Ubuntu 22.04 laptop with two SSDs. Most of my 3d-models are on the second disk but for whatever reason, the version 2.9.0. does not want to 'see' that disk:-( Even when I try to cd into the directory with all the *.stl files, and try to start with one on the command line, the slicer says 'File not found' :-(
The 2.8.1 AppImage did not have that problem. All the permissions work for the last couple of years ...
I don't know, if that is a feature of the flatpack setup or what's going on ?!
Project file & How to reproduce
File -> Open -> Other Locations -> Computer and my /disk1 is not even listed:-(
Checklist of files included above
Version of PrusaSlicer
Version 2.9.0 Linux flatpack
Operating system
Ubuntu 22.04 - fully patched
Printer model
MK4SMMU3, MK3S, Creality Ender3V2
The text was updated successfully, but these errors were encountered: