Skip to content
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

Can not access directories which are symbolic links. #13820

Open
2 tasks done
dhpinkerton opened this issue Dec 21, 2024 · 9 comments
Open
2 tasks done

Can not access directories which are symbolic links. #13820

dhpinkerton opened this issue Dec 21, 2024 · 9 comments
Labels

Comments

@dhpinkerton
Copy link

Description of the bug

When importing a STL file I can no longer access symlink directories.

File -> Import -> Import STL

My Documents directory is no longer visible.

As per attached screen shots.

I also can no longer Export G-code to a symlink directory.

No longer able to open an STL file by double clicking the file. No longer any Desktop Intergration?

Project file & How to reproduce

PrusaSlicer-BugReport_DHP.zip

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

Version 2.9.0

Operating system

Fedora 41

Printer model

Creality Ender 5 Pro

@theopensourcerer
Copy link

+1. Affecting me too. Just installed 2.9.0 using flatpak and I can't access my "projects" directory which is a symlink to another physical drive on my PC. Am running Ubuntu 20.04.

@jantastique
Copy link

+1 same here. 2.9.0 flatpak Mint 22.
NFS shares are not available for import. Receiving "Loading of model file failed" by drag & drop from NFS.
Basically it seems I'm only able to access files in my home directory.

@jantastique
Copy link

+1 same here. 2.9.0 flatpak Mint 22. NFS shares are not available for import. Receiving "Loading of model file failed" by drag & drop from NFS. Basically it seems I'm only able to access files in my home directory.

ok, I figured out the behavior in my case appears due to the sandbox restictions of flatpak. So I needed to add --filesystem=/mnt/path/to/workingdir to the command line starting the app (see Flatpak permissions).

I successfully tested this with symlinks as well, by adding their paths as described.

Since I have no experience with flatpak (actually avoiding it whenever possible), I can't tell if this is a good solution, but works for me in this case.

@dhpinkerton
Copy link
Author

I've managed to fix mine by...

flatpak override --user --filesystem=host com.prusa3d.PrusaSlicer

To give the app access to all filesystems.

@SachCZ
Copy link
Collaborator

SachCZ commented Dec 27, 2024

Hello, as you correctly determined, this is a flatpak permissions issue. Personally I would recommend flatseal to permanently add paths you want.

Screenshot from 2024-12-27 12-01-07

@vxrexx
Copy link

vxrexx commented Dec 29, 2024

I have a similar error: network drives (which are connected to Gigolo) can no longer be used, they are no longer displayed.
(Debian 12.8)

@andrewmeyer
Copy link

can confirm, this is a permissions issue I was able to fix via flatseal, thank you @SachCZ

@dbyy
Copy link

dbyy commented Jan 6, 2025

I've managed to fix mine by...

flatpak override --user --filesystem=host com.prusa3d.PrusaSlicer

To give the app access to all filesystems.

I think there is another problem with the new version of Prusaslicer (v2.9.0).

  1. the problem which lies actually with flatpak = access permission to directory on a NAS drive.
  2. the problem with the pre-selection of file extension in the "import file" dialog (CTRL-I). I'm using a symlink on my home drive which is pointing to the directory on a NAS drive where all my models are located. Since the pre-selected file extension in this dialog (the DDL) makes it impossible to activate this link (to the NAS). The DDL should have an option "all file types" which would make the symlink visible. Then, with the required permissions set in flatpak, I could easily access all my models.
    Does that makes sense?
    Would that be a feature request or a reported bug?

@SachCZ
Copy link
Collaborator

SachCZ commented Jan 7, 2025

Hello @dbyy,
Addressing the second problem:
Was it ever the case that the link was visible? If so then it is a bug. Otherwise it is a feature request. In any case please create a new issue. As this one is fixed by fixing permissions for the OP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants