{"action":"created","issue":{"url":"https://api.github.com/repos/flathub/org.gimp.GIMP/issues/11","repository_url":"https://api.github.com/repos/flathub/org.gimp.GIMP","labels_url":"https://api.github.com/repos/flathub/org.gimp.GIMP/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/flathub/org.gimp.GIMP/issues/11/comments","events_url":"https://api.github.com/repos/flathub/org.gimp.GIMP/issues/11/events","html_url":"https://github.com/flathub/org.gimp.GIMP/issues/11","id":319352833,"number":11,"title":"Can't access files in /tmp","user":{"login":"ofnuts","id":10837436,"avatar_url":"https://avatars2.githubusercontent.com/u/10837436?v=4","gravatar_id":"","url":"https://api.github.com/users/ofnuts","html_url":"https://github.com/ofnuts","followers_url":"https://api.github.com/users/ofnuts/followers","following_url":"https://api.github.com/users/ofnuts/following{/other_user}","gists_url":"https://api.github.com/users/ofnuts/gists{/gist_id}","starred_url":"https://api.github.com/users/ofnuts/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ofnuts/subscriptions","organizations_url":"https://api.github.com/users/ofnuts/orgs","repos_url":"https://api.github.com/users/ofnuts/repos","events_url":"https://api.github.com/users/ofnuts/events{/privacy}","received_events_url":"https://api.github.com/users/ofnuts/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-05-01T22:45:39Z","updated_at":"2018-05-06T19:48:48Z","closed_at":"2018-05-01T23:11:51Z","author_association":"NONE","body":"I cannot open files in `/tmp`. The directory appears in the file selector but is empty. As far as I can tell I can access all other directories. I can save/export files to `/tmp` and re-open them, but this isn't the real `/tmp` in my system (and seems to be reinitialized when the application is closed/restarted). I would guess there is some `/tmp` in the flatpak that masks the true `/tmp`. Couldn't that one have a special name to avoid masking that very useful directory? "},"comment":{"url":"https://api.github.com/repos/flathub/org.gimp.GIMP/issues/comments/386908125","html_url":"https://github.com/flathub/org.gimp.GIMP/issues/11#issuecomment-386908125","issue_url":"https://api.github.com/repos/flathub/org.gimp.GIMP/issues/11","id":386908125,"user":{"login":"Jehan","id":794997,"avatar_url":"https://avatars0.githubusercontent.com/u/794997?v=4","gravatar_id":"","url":"https://api.github.com/users/Jehan","html_url":"https://github.com/Jehan","followers_url":"https://api.github.com/users/Jehan/followers","following_url":"https://api.github.com/users/Jehan/following{/other_user}","gists_url":"https://api.github.com/users/Jehan/gists{/gist_id}","starred_url":"https://api.github.com/users/Jehan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Jehan/subscriptions","organizations_url":"https://api.github.com/users/Jehan/orgs","repos_url":"https://api.github.com/users/Jehan/repos","events_url":"https://api.github.com/users/Jehan/events{/privacy}","received_events_url":"https://api.github.com/users/Jehan/received_events","type":"User","site_admin":false},"created_at":"2018-05-06T19:48:48Z","updated_at":"2018-05-06T19:48:48Z","author_association":"COLLABORATOR","body":"> /tmp is used by processes to share files. For instance, the \"Spectacle\" screencapture in KDE will save the file in /tmp before calling Gimp if I ask it to \"Export to Gimp\".\r\n\r\nYes but it doesn't matter here. Either both software are in the flatpak and they share a `/tmp/` (even though not the `/tmp/` as the rest of the system), either they are not and anyway won't interact with each other (not entirely true though; they could, for instance through dbus, etc.).\r\n\r\n> how do I know if fixes for flatpak issues are available (in other words how/when I can update my version)\r\n\r\nJust update whenever you can, and if there are fixes, the update will pull the rebuilt GIMP. If your distribution has built-in flatpak support, it may even propose you to update from time to time (together with other updates of the system).\r\n\r\n> I noticed that the Gimp download page for Linux is now considering flatpak as the standard delivery/install mechanism\r\n\r\nSomeone else made the remark that it is the recommended installation for Linux. It is not the case (not yet). On the download page, there is even this text clearly saying:\r\n\r\n> The flatpak build is very new and therefore may have shortcomings. It's very likely your Unix-like system distribution already comes with a GIMP package. It is the preferred method of installing GIMP, as the distribution maintainers take care of all the dependencies and bug fix updates. Nevertheless, note that many distros decide to pin a specific version of GIMP to their releases, whereas our flatpak will follow GIMP releases closely.\r\n\r\nThe flatpak technology is new, and GIMP in flatpak has several feature losses (that we know of already, I'm sure we may discover more as time goes). Some feature losses can probably be fixed on our side by tweaking the flatpak, but several are either limitations of the sandbox model, or implementations which will need to happen on flatpak side (as examples, using darktable/RawTherapee as raw plug-ins of GIMP doesn't work because of sandbox model, and midi device support is broken as well, there is a [bug report](https://github.com/flatpak/flatpak/issues/12) about it, and I am not really optimist about a resolution soon).\r\n\r\nSo no, as it stands, flatpak is not the most recommended way. It may become some day. We'll have to see how things evolve. But currently, the only possible full-featured GIMP is still made by old-school packages.\r\nWhy the flatpak build is prominent on our download page is only because that's the only thing we can propose, since the recommended way is not maintained by us, by definition. It is maintained by distributions.\r\n\r\n> so should flatpak problems be reported on bugzilla.gnome.org? And if so shouldn't there be a \"flatpak\" component?\r\n\r\nI wondered about this too. This would make sense. On the other hand, the flathub infrastructure currently forces us to have a github repository, which comes with its own bug tracker, etc. So if we were to duplicate all the report points, this becomes a bit messy (this being said, several people already reported bugs related to flatpak package on bugzilla, so…). Well in the very end, I don't really know!\r\nI wished we could have just tracked our flatpak source in GIMP repo as everything else. This would be less of a mess."}}
{"actor":{"display_login":"Jehan"}}