Skip to content
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

Not aware of rawtherapee and darktable when all is installed as flatpak #138

Open
yajo opened this issue Feb 21, 2022 · 7 comments
Open

Comments

@yajo
Copy link

yajo commented Feb 21, 2022

I tried to open a raw picture.

A dialog appeared saying:

Opening '/var/home/yajo/Imágenes/Fotos compartidas/2022-02-19 Sesión de fotos/IMG_9528.CR2' failed: There is no RAW loader installed to open 'Raw Canon' files.

GIMP currently supports these RAW loaders:

Please install one of them in order to load RAW files.

I have both of those apps installed, but they are flatpaks, just like GIMP.

So GIMP flatpak should be somehow aware of these other apps when all is installed as flatpaks AFAICS.

@Jehan
Copy link
Collaborator

Jehan commented Feb 21, 2022

Yes by sandbox-logic, a software doesn't see outside its box, and in particular, it doesn't see other software. For such features, it requires "portals", but there is currently no portal to run other flatpaks.

I know there is a report somewhere about making such a portal. I can't find the link right now. Anyway the day when it will become a reality, we'll have to use this to allow this feature. In the meantime, it is just not possible by technology limitation.

@yajo
Copy link
Author

yajo commented Feb 21, 2022

However there must be a way, don't you think? because Flatseal can see what other flatpak apps exist installed, and even manage their permissions.

I guess It'll be around this: https://github.com/flathub/com.github.tchx84.Flatseal/blob/9156b312e6fa1a9087e8a3746fe6c48715ae1b8a/com.github.tchx84.Flatseal.json#L13-L14

@Jehan
Copy link
Collaborator

Jehan commented Feb 21, 2022

@yajo As you can see from the link you give, the way flatseal works (which was also what I understood reading info about it, though I never looked in the code) is that they have access to the flatpak directories directly. This is even very precisely the 2 lines you give yourself.

This has absolutely no interest for us, unless we also wanted to edit the other flatpak-s directly. It doesn't give us magically the ability to run them, then get returned files back from these software. Or well… if it did, there would be quite a serious leak to fix!

Flatseal does not run other flatpak, it doesn't interact with them. It only modifies their files.

@yajo
Copy link
Author

yajo commented Feb 22, 2022

Ah I see... Then maybe GIMP should use the open portal directly or something like that?

For example, I installed Evolution. When an email has an attached image, I can double-click on it, and a dialog will appear asking me with which app I want to open it. It lists all apps that open images, no matter if flatpak or not:

imagen

But then I guess that should be upstream issue, right?

@Jehan
Copy link
Collaborator

Jehan commented Feb 22, 2022

This is again a different concept. It allows to open an image (or any file) in another software, and then it's over. What we do in GIMP is a roundtrip as part of a workflow. We send file to raw image developers (darktable, RawTherapee) then once the work there is done, it comes back in GIMP to be able to continue the work there. It's a collaboration mechanism to make use of the power of several powerful application in a more flowing process.

Just opening it in another software (then the image is gone) while it is opened in GIMP doesn't make really much sense. Just open it directly in darktable or RawTherapee, then later export it from these software and open the exported file in GIMP if that's what you want. Because this is exactly what you are asking in this last comment, except that you want to add one step to this workflow. ;-)

@yajo
Copy link
Author

yajo commented Feb 25, 2022

Ok that's what I did. I thought there was some deeper integration I was missing 😁
Thanks!

@yajo yajo closed this as completed Feb 25, 2022
@Jehan
Copy link
Collaborator

Jehan commented Feb 25, 2022

Let me reopen this report as a reminder though. We still want the collaboration process to be possible, it's simply not possible right now as far as we know. So it's good we have a tracking report about this issue.

@Jehan Jehan reopened this Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants