Save function is broken on flatpak

[nescioquid]

Save function is broken on flatpak

[JakobDev]

I'm the Maintainer of the Flatpak. I can't the reproduce this on Manjaro KDE. Did you open the Project with File>Open project or did you another method?

[nescioquid]

that's been what I've been doing, but now that I check, I can't select the repo and choose to Open With, as it doesn't list porymap as a program in that menu. perhaps the program has only read-only access? have there been issues like that before?

EDIT: porymap.log

it looks like it can't open, and then it's also not getting permission to write to the files. for what it's worth, the actual directory location for wild encounters is at ~/builds/pokemon/not-new-emerald/src/data/wild_encounters.json (for wild encounters obviously).

EDIT 2: I'm on version 5.1.1. also, I had auto login on which is known to cause some other authentication issues down the line on PopOS, but disabling it and logging in at top level had no effect on the bug.

[JakobDev]

PopOS should give the Flatpak Write Permission to that Directory, when you select it. But that did not work for some reason. You should write a Bug Report. In the meantime, you should use Flatseal to give Porymap write permission for the Host System to fix the Issue.

[nescioquid]

will do, but would that be a report to PopOS or flatpak?

also, I'm not the most sophisticated user, but with flatseal I've given Porymap all filesystem permissions, including for the exact /run/user/1000/doc/24f5f1f9/not-new-emerald directory specified in the logs:

• all system files
• all system libraries, executables, and static data
• all system configurations
• all user files
• other files
  • /run/user/1000/doc/24f5f1f9/not-new-emerald
  • xdg-config/kdeglobals:ro

this last file, xdg-config/kdeglobals:ro, was already specificied in flatseal before I edited permissions.

I'm going to keep poking around with the permissions, but which settings would you expect to be minimum necessary? I would of course prefer to limit them as much as possible.

[nescioquid]

I was able to get a wild encounter edit to save successfully, but I both gave the program every toggleable permission possible and reopened the project. will edit this comment with more details as they come, but thanks!

EDIT: it looks like only permissions for all user files and a reload of the project were necessary to get things working. thank you so much! again please let me know if I should create a bug report with PopOS or Flatpak or both. :)

[JakobDev]

You should report to PopOS. The Bug is part of the xdg-desktop-portals which are implemented by each Desktop,

I'm going to keep poking around with the permissions, but which settings would you expect to be minimum necessary? I would of course prefer to limit them as much as possible.

Just give permission to the Directory you are opening.

[nescioquid]

yes I did so, it's been working like a charm! the linux version seems to run a lot more smoothly than on windows. thanks again!

---

(also while I'm here: I know you're the flatpak mantainer, but the windows version doesn't appear to support dark mode, or at least I couldn't get it to work. cheers!)

[JakobDev]

Is the Dark Theme in the settings not available on Windows?

[garakmon]

Should be