| Summary: | kio-fuse randomly named directory makes working with flatpaks difficult | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kiofuse | Reporter: | Jason Straight <j.straight-kde> |
| Component: | general | Assignee: | a.saoutkin |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | fabian, kio-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
> Accessing remote filesystems with flatpaks is a pain due to the fuse mountpoint being random at every use. Why do you pass --filesystem manually instead of using portals? In any case, there's https://invent.kde.org/system/kio-fuse/-/issues/18 with some more discussion. (In reply to Fabian Vogt from comment #1) > Why do you pass --filesystem manually instead of using portals? I'm unsure how to use portals in this context. I thought that portals in flatpak were accessible via the API's and were something the desktop environment or developer would implement use of. I don't seem to be able to find any useful information for an end user to use portals to solve this kind of problem. If you have a source, I'd appreciate a link or two. Thanks. > In any case, there's https://invent.kde.org/system/kio-fuse/-/issues/18 with > some more discussion. Thank you. (In reply to Jason Straight from comment #2) > (In reply to Fabian Vogt from comment #1) > > Why do you pass --filesystem manually instead of using portals? > > I'm unsure how to use portals in this context. I thought that portals in > flatpak were accessible via the API's and were something the desktop > environment or developer would implement use of. > > I don't seem to be able to find any useful information for an end user to > use portals to solve this kind of problem. The API is used to open files from the host file system. In file open dialogs you can navigate to any location and select also files inside kio-fuse mounts. (In reply to Fabian Vogt from comment #3) > The API is used to open files from the host file system. In file open > dialogs you can navigate to any location and select also files inside > kio-fuse mounts. Whenever I navigate to the xdg-run folder the kio-fuse-* folder is not present to the file dialog in any non kde program. Maybe my OpenSuSE is missing a required GTK package. So it appears that portals only work with certain file choosers, and the programs I'm trying to use remotely don't use [the standard GTK one](https://blogs.gnome.org/mclasen/2016/07/08/portals-using-gtk-in-a-flatpak/), I'm guessing. I was able to access the kio-fuse-* folder from some gnome apps. So, this will probably remain to be an issue with several apps. After following this down the rabbit hole, I'm convinced this is something that would be a non-issue if flatpak/gtk worked like it was supposed. Not a KDE/kiofuse problem. Thanks for pointing me in that direction. |
Accessing remote filesystems with flatpaks is a pain due to the fuse mountpoint being random at every use. I order to access a remote filesystem with a flatpak program, like brackets, you have to run it like flatpak run --filesystem=xdg-run/kio-fuse-OexuTR io.brackets.Brackets The fact that kio-fuse-OexuTR is different every time really complicates this. Why is this necessary? I don't think gvfs does it this way.