-
Notifications
You must be signed in to change notification settings - Fork 214
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't load/save files from Samba gvfs mount #913
Comments
Can you try using flatseal to allow access to those directories? |
OK that probably won't help since we already have |
Adding in "others files" those paths (as ex. in Inkscape):
it helps and enable drag and drop from samba path.
it does nothing (at least for what I have tested). But saving is still impossible (yes, I have all the write and read permissions on the remote folder :) ) and no warning. Thank you, |
I can reproduce it, just found the details here: https://docs.flatpak.org/en/latest/sandbox-permissions.html#gvfs-access Note that we need gvfs instead of gvfsd which would be recommended for Gtk applications. I guess we are not using the built in functions to read/write files, therefore we are not a Gtk application in this regard. When saving I get this error on the CLI:
TODO:
|
Well I managed to do some debuggin inside the flatpak and the result is that Gtk.FileChooserNative just returns None as Filename when selecting a file from a samba share. pdfarranger/pdfarranger/pdfarranger.py Lines 1090 to 1119 in 118bfc1
According to the error message it runs through 1119 so the response must be "accept". I also see this in my system log:
|
Btw this is probably the same when opening, we just don't get to see an error message. The documentation actually says:
This led me to the suspicion that Gtk has issues finding a local filename for this file. This seems to be the issue: Selecting the file through some fancy looking samba mountpoint doesn't work but once you click manually through to the |
I imagined it was an upstream problem. Thank you, |
Yes, I'm afraid that's all we can do for now. I subscribed to both bugs, thankfully there already is a PR upstream. Once that is merged we could have a look whether that is going to cascade through the PDF Arranger flatpak or your distro, but I think it will be the latter. As a workaround you can give access through flatseal and then navigate the /run/... path in the open/close dialogs, that worked for me but it is of course cumbersome. I'd try creating a symlink from a convenient location, that might work just fine. ( |
Thank you, for the moment I had the opportunity to switch to Debian package. Thank you, |
The fix for this has been merged and even backported to Gnome 45. Are you using Gnome 45? Not sure how fast those updates trickle through but it might be worth checking this again in a few weeks. Original merge request: https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/merge_requests/67 |
@canonex could you check whether this is fixed with your latest os updates? |
Option A is solved: Option B and C are not solved: Tests are done by installing the flatpack from scratch, without changing permissions on folders (eg. flatseal). Thank you, |
Describe the bug
Ambiguous behavior using Pdf arranger flatpak with Samba.
The scenario is the need, in an office or home with a Nas where there are Samba network shares, to edit Pdfs directly from the share without having to copy them locally.
On Gnome (Debian 12 Bookworm) the shares are correctly mounted with gio mount (see attached image) and all file operations can be correctly performed using Nautilus.
To Reproduce
Steps to reproduce the behavior option A:
Steps to reproduce the behavior option B:
Steps to reproduce the behavior option C:
Expected behavior
The ability to properly use Pdf arranger on gio mount shares or a clear message indicating that remote files are not supported.
Screenshots
System and Versions
Please not that that the bug is not present installing the Debian version, it seems to me it is just a flatpak issue.
Thanks a lot, it's really a cool software :)
Riccardo
The text was updated successfully, but these errors were encountered: