You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the installation of PrusaSlicer 2.9, I attempted to open my last project. However, I encountered an issue: the open file dialog window is unable to access the '/mnt/' path and generates "Loading of model failed". This behavior differs from version 2.5, where I could navigate to any location within the system. Furthermore, attempting to drag and drop the model file directly from the Nemo file explorer results in the error 'Loading of model file failed.
Project file & How to reproduce
File->Open-> "trz navigate to /mnt/"
Checklist of files included above
Project file
Screenshot
Version of PrusaSlicer
2.9
Operating system
Linux meny-HP-8760w 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Printer model
Reduplikator
The text was updated successfully, but these errors were encountered:
Please search existing issues before opening new ones. This is a duplicate of #13844 or #13862 for example. Please see this specific comment on how to solve your issue #13844 (comment)
Description of the bug
Following the installation of PrusaSlicer 2.9, I attempted to open my last project. However, I encountered an issue: the open file dialog window is unable to access the '/mnt/' path and generates "Loading of model failed". This behavior differs from version 2.5, where I could navigate to any location within the system. Furthermore, attempting to drag and drop the model file directly from the Nemo file explorer results in the error 'Loading of model file failed.
Project file & How to reproduce
File->Open-> "trz navigate to /mnt/"
Checklist of files included above
Version of PrusaSlicer
2.9
Operating system
Linux meny-HP-8760w 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Printer model
Reduplikator
The text was updated successfully, but these errors were encountered: