-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
OPML export fails/complicated due to SailJail #209
Comments
…ions fixes gpodder#209 (or works around it) Not tested.
Interesting, I guess because I have it installed over many versions I have more permissions grandfathered in, adding a Sailjail profile has been on my list of things I want to get to for a while, just didn't have priority since things seemed to be working regardless. Can you explain a bit more why you think |
My view is that |
Yes, you are right. Option b) seemed just to be the easier option. |
- Audio - UserDirs - since we allow the user to change the Downloads directory - RemovableMedia - same as UserDirs - Internet It is unclear to me if UserDirs also includes ~, if not we will need to update the export code to fix gpodder#209 Signed-off-by: E.S. Rosenberg a.k.a. Keeper of the Keys <es.rosenberg+gpodder@gmail.com>
Current Sailfish OS versions enforce sailjail/firejail rules.
When one tries to export the list of podcasts into an OPML file, gpodder asks for a filename (i.e. does not present a folder selection screen).
The file is then saved into the user's home directory with a ".opml" extension.
However, the exported file never reaches the actual home directory but stays in the sailjail/firejail container and is lost when gpodder is closed.
As far as I understand the issue, gpodder would either
/etc/sailjail/permissions/UserDirs.permission
(e.g., Documents, Downloads, or Music) or to the SD cardWorkaround: enter
Documents/export.opml
in the file name field when exporting the podcasts.Alternative workaround (tried this first before looking into permissions; adjust the path to only get the .opml file you want):
The text was updated successfully, but these errors were encountered: