sjostrand@sjostrand:/mnt/80ae89cb-968f-4fc6-9262-0017685bc03f/Photo$ rawtherapee /mnt/80ae89cb-968f-4fc6-9262-0017685bc03f/Photo
Command ‘rawtherapee’ not found, but can be installed with:
sudo apt install rawtherapee
sjostrand@sjostrand:/mnt/80ae89cb-968f-4fc6-9262-0017685bc03f/Photo$
I beleive it the plathub version of RawTherapee that does not work propper
How install Raw Therapee 5.8 ?? because Kubuntu does not have RaW therapee 5.8
If you don’t have RawTherapee installed, how were you running it the whole time?
This might be solid *buntu advise, although I previously understood Kubuntu uses dpkg.
i did have it install from flathub. But this version is something wrong with, because the Appimage of RT works.
How can I install RT from developer direct because Kubuntu Programstore dos not have RT 5.8
You should have mentioned this 58 posts ago. You’re running some unofficial build - it’s not from the RawTherapee website, and it’s not from your distribution’s package manager.
Two ways forward:
So perhaps there is an issue with GitHub - flathub/com.rawtherapee.RawTherapee ping @paperdigits
ye i think so but i don’t like appimages because not easy too update
But i don’t have another choice
RawTherapee’s AppImage has a self-update mechanism, not sure how to invoke it though.
Maybe:
./RawTherapee_5.8.AppImage --enable-auto-update
@Carmelo_DrRaw would know.
Thanks
BIG Thanks to All for this great help and experience for me as newbee on linux!
Yes, hello. The flatpak of RT is sandboxed and by default only allowed to access your home directory and /tmp.
You can override the sandbox like this: flatpak --user override --filesystem=/path/to/filesystem com.rawtherapee.RawTherapee or grab the app Flatseal, which will give you a GUI for managing flatpak permissions.
Thank you, Mica. The macOS bundle I generate is also sandboxed but entitled by signature to access / during the runtime. This is known as a temporary exception in the 
world. Is the limitation due to a flatpak organizational rule? If not I would consider looking for such an entitlement.
For flathub, they ask that the file system access is limited as much as possible, but it is still up to each developer. I think the access is reasonable, and flatpak gives control to the user to decide where to allow access. The user can grant permenant or temporary access through the sandbox.
Now, we can make our own flatpaks and grant whatever access we want…
I am one of the flatpak maintainers on flathub, so ask away!
“as much as possible”
I think access to /mnt definitely fits there. Is that possible with a flatpak sandbox? /mnt might be too Kubuntu-specific but you get the drift.
From what I know, different distros/apps will mount things in different places. Fedora does it in /run/media/username, Ubuntu in /mnt/username, gvfs mounts its own way… and then there is the mount command.
On Mac every logical drive is always in /Volumes and there’s only one distro of macOS. The / entitlement I can browse into a flash drive, a folder, bundle or container in any of various subdirectories of / reducing the chance of a null action when clicking on a file-type associated with the app, etc. Can flatpaks also behave specifically according to the distro of the user?
Not that I’m aware of.
dpkg is the underlying package manager, but apt/apt-get is kind a second layer above it that usually makes everything much easier.
(Not sure if you can do something like automatically fetch and install all dependencies with dpkg alone without apt)
I think the way to describe it is that apt is to dpkg as yum is to RPM?
No, you can’t do that with dpkg.
Correct.