I wanted to start a new thread, with the intend to spiffing up the README file that Gilles started on https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak Here is my writeup, still a little KDE (kubuntu w/ plasma) centric, but with the intent to be command line driven as much as possible. I invite anybody to comment and me or somebody will edit the README.md file You need admin permission to install the flatpak infrastructure sudo apt install flatpak flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo and on Kubuntu there is a optional GUI based discovery tool sudo apt install plasma-discover-flatpak-backend after rebooting (it claims), you can then do your user installs flatpak install flathub org.kde.digikam This will install your apps in ~/.var/app. Also perhaps import that note that any config files live there (e.g. ~/.var/app/org.kde.digikam/config/digikamrc and your settings in ~/.config/digikamrc are out of visibility) running the app goes as follows flatpak run org.kde.digikam Since flatpak's run in a restricted environment, you will find that not all directories can be see by the digikam collections (/home and /media are exceptions), and you will not be able to launch gimp for example. To edit these settings there is flatseal to the rescue: flatpak install flathub flatseal which I then read you can either use a command line (but as root, this I still find confusing) sudo flatpak override org.kde.digikam --filesystem=/Photos or use the GUI "launch flatseal, select digiKam", add to "Other files" or select "All system files" Those will be stored in ~/.local/share/flatpak/overrides/org.kde.digikam now you can run flatpack and see your oddly named /Photos directory flatpak run org.kde.digikam More information on flatpak, and flatseal permission settings on https://www.linux.com/training-tutorials/how-install-and-use-flatpak-linux/ https://docs.flatpak.org/en/latest/sandbox-permissions.html |
Just to point out that openSUSE installs flatpak by default, at least it
does on Tumbleweed. Also if you use the command line to override the filesystem to allow directory access flatseal does not see the override when you start it. Also found at leats on Tumbleweed when installing digikam it overwrites the menu entry for digikam if already installed via your OS. Stuart On 01/06/2020 17:30, Peter Teuben wrote: > > I wanted to start a new thread, with the intend to spiffing up the > README file that Gilles started on > https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak > > > Here is my writeup, still a little KDE (kubuntu w/ plasma) centric, but > with the intent to be command line driven as much as possible. I invite > anybody to comment and me or somebody will edit the README.md file > > > > > You need admin permission to install the flatpak infrastructure > > sudo apt install flatpak > flatpak remote-add --if-not-exists flathub > https://flathub.org/repo/flathub.flatpakrepo > > and on Kubuntu there is a optional GUI based discovery tool > > sudo apt install plasma-discover-flatpak-backend > > after rebooting (it claims), you can then do your user installs > > flatpak install flathub org.kde.digikam > > This will install your apps in ~/.var/app. Also perhaps import that > note that any config > files live there (e.g. ~/.var/app/org.kde.digikam/config/digikamrc and > your settings in > ~/.config/digikamrc are out of visibility) > > running the app goes as follows > > flatpak run org.kde.digikam > > Since flatpak's run in a restricted environment, you will find that not > all directories > can be see by the digikam collections (/home and /media are exceptions), > and you will not > be able to launch gimp for example. To edit these settings there is > flatseal to the rescue: > > flatpak install flathub flatseal > > which I then read you can either use a command line (but as root, this I > still find confusing) > > sudo flatpak override org.kde.digikam --filesystem=/Photos > > or use the GUI > > "launch flatseal, select digiKam", add to "Other files" or select > "All system files" > Those will be stored in > ~/.local/share/flatpak/overrides/org.kde.digikam > > now you can run flatpack and see your oddly named /Photos directory > > flatpak run org.kde.digikam > > More information on flatpak, and flatseal permission settings on > > https://www.linux.com/training-tutorials/how-install-and-use-flatpak-linux/ > https://docs.flatpak.org/en/latest/sandbox-permissions.html > > > > > > > -- Website: https://www.stella-maris.org.uk or: https//www.broadstairs.org |
In reply to this post by Peter Teuben
Hello Peter, Thank you for posting the readme here. You mentioned that digiKam flatpak is not able to open GIMP. Does that mean that "Open With" menu won't work at all? If that is the case it will a deal breaker for most of us then. I am sure most users use digikam in conjunction with exiftool, ffmpeg, mediainfo, GIMP, Kdenlive, Krita, darktable, RawTherapee and others. Even the ability to locate selected file in dolphin or other file manager seems crucial (to me). Thanks, Andrey On Mon, Jun 1, 2020 at 10:31 AM Peter Teuben <[hidden email]> wrote:
|
Andrey, The "open with" works, but has very few entries. Remember it sits in a restricted environment. So even trying /usr/bin/gimp does not work, even though it's there. And I even have the whole filesystem open now. Perhaps this is
another setting in flatseal that I haven't discovered, and that'
why we are talking here , to get those final issues I have out of
the way. After that I'm happy to submit a ppull request, but I
think the one I have now is getting pretty close. thanks for all
the feedback, I've learned a great deal. peter On 6/1/20 1:12 PM, Andrey Goreev wrote:
|
In reply to this post by AndriusWild
These programs only appear by default if you install them with flatpak. You can open up the flatpak system to allow access to existing programs but I'm not sure exactly how, I think you have to add the paths to them.
Stuart On 1 June 2020 18:12:29 BST, Andrey Goreev <[hidden email]> wrote: >Hello Peter, >Thank you for posting the readme here. >You mentioned that digiKam flatpak is not able to open GIMP. Does that >mean >that "Open With" menu won't work at all? >If that is the case it will a deal breaker for most of us then. I am >sure >most users use digikam in conjunction with exiftool, ffmpeg, mediainfo, >GIMP, Kdenlive, Krita, darktable, RawTherapee and others. Even the >ability >to locate selected file in dolphin or other file manager seems crucial >(to >me). > >Thanks, >Andrey > > >On Mon, Jun 1, 2020 at 10:31 AM Peter Teuben <[hidden email]> wrote: > >> >> I wanted to start a new thread, with the intend to spiffing up the >> README file that Gilles started on >> >> >https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak >> >> Here is my writeup, still a little KDE (kubuntu w/ plasma) centric, >but >> with the intent to be command line driven as much as possible. I >invite >> anybody to comment and me or somebody will edit the README.md file >> >> >> >> >> You need admin permission to install the flatpak infrastructure >> >> sudo apt install flatpak >> flatpak remote-add --if-not-exists flathub >> https://flathub.org/repo/flathub.flatpakrepo >> >> and on Kubuntu there is a optional GUI based discovery tool >> >> sudo apt install plasma-discover-flatpak-backend >> >> after rebooting (it claims), you can then do your user installs >> >> flatpak install flathub org.kde.digikam >> >> This will install your apps in ~/.var/app. Also perhaps import that >> note that any config >> files live there (e.g. ~/.var/app/org.kde.digikam/config/digikamrc >and >> your settings in >> ~/.config/digikamrc are out of visibility) >> >> running the app goes as follows >> >> flatpak run org.kde.digikam >> >> Since flatpak's run in a restricted environment, you will find that >not >> all directories >> can be see by the digikam collections (/home and /media are >exceptions), >> and you will not >> be able to launch gimp for example. To edit these settings there is >> flatseal to the rescue: >> >> flatpak install flathub flatseal >> >> which I then read you can either use a command line (but as root, >this I >> still find confusing) >> >> sudo flatpak override org.kde.digikam --filesystem=/Photos >> >> or use the GUI >> >> "launch flatseal, select digiKam", add to "Other files" or >select >> "All system files" >> Those will be stored in >> ~/.local/share/flatpak/overrides/org.kde.digikam >> >> now you can run flatpack and see your oddly named /Photos directory >> >> flatpak run org.kde.digikam >> >> More information on flatpak, and flatseal permission settings on >> >> >https://www.linux.com/training-tutorials/how-install-and-use-flatpak-linux/ >> https://docs.flatpak.org/en/latest/sandbox-permissions.html >> >> >> >> >> >> >> -- Sent from my Samsung Galaxy J5 with K-9 Mail. Please excuse my brevity. |
In reply to this post by Stuart T Rogers
Another surprise (at least for Kubuntu): I installed both the flatpak
and the native app. And the GUI launcher where you type "digikam" only shows one, the beta luckily. But on the command line i can still execute digikam natively. This sounds like a bug to me inthe Kubuntu system (or it's yet another setting) How do others fare here, dare I ask ? It should be commented (and I will do that) that if you are running both, they will perhaps look at the same digikam4.db file, and this could lead to surprises. I keep a backup in case it got mangled, which it did in my case before I knew about the flatseal permissions I needed, as I lost whole albums and they would need to be rebuilt! - peter On 6/1/20 1:04 PM, Stuart T Rogers wrote: > Just to point out that openSUSE installs flatpak by default, at least > it does on Tumbleweed. Also if you use the command line to override > the filesystem to allow directory access flatseal does not see the > override when you start it. > > Also found at leats on Tumbleweed when installing digikam it > overwrites the menu entry for digikam if already installed via your OS. > > Stuart > > On 01/06/2020 17:30, Peter Teuben wrote: >> >> I wanted to start a new thread, with the intend to spiffing up the >> README file that Gilles started on >> https://invent.kde.org/graphics/digikam/-/tree/master/project/bundles/flatpak >> >> >> Here is my writeup, still a little KDE (kubuntu w/ plasma) centric, >> but with the intent to be command line driven as much as possible. I >> invite anybody to comment and me or somebody will edit the README.md >> file >> >> >> >> >> You need admin permission to install the flatpak infrastructure >> >> sudo apt install flatpak >> flatpak remote-add --if-not-exists flathub >> https://flathub.org/repo/flathub.flatpakrepo >> >> and on Kubuntu there is a optional GUI based discovery tool >> >> sudo apt install plasma-discover-flatpak-backend >> >> after rebooting (it claims), you can then do your user installs >> >> flatpak install flathub org.kde.digikam >> >> This will install your apps in ~/.var/app. Also perhaps import that >> note that any config >> files live there (e.g. ~/.var/app/org.kde.digikam/config/digikamrc >> and your settings in >> ~/.config/digikamrc are out of visibility) >> >> running the app goes as follows >> >> flatpak run org.kde.digikam >> >> Since flatpak's run in a restricted environment, you will find that >> not all directories >> can be see by the digikam collections (/home and /media are >> exceptions), and you will not >> be able to launch gimp for example. To edit these settings there is >> flatseal to the rescue: >> >> flatpak install flathub flatseal >> >> which I then read you can either use a command line (but as root, >> this I still find confusing) >> >> sudo flatpak override org.kde.digikam --filesystem=/Photos >> >> or use the GUI >> >> "launch flatseal, select digiKam", add to "Other files" or >> select "All system files" >> Those will be stored in >> ~/.local/share/flatpak/overrides/org.kde.digikam >> >> now you can run flatpack and see your oddly named /Photos directory >> >> flatpak run org.kde.digikam >> >> More information on flatpak, and flatseal permission settings on >> >> https://www.linux.com/training-tutorials/how-install-and-use-flatpak-linux/ >> >> https://docs.flatpak.org/en/latest/sandbox-permissions.html >> >> >> >> >> >> >> > |
On lundi 1 juin 2020 19:38:09 CEST Peter Teuben wrote:
> Another surprise (at least for Kubuntu): I installed both the flatpak > and the native app. And the GUI launcher where you type "digikam" only > shows one, the beta luckily. But on the command line i can still > execute digikam natively. > > This sounds like a bug to me inthe Kubuntu system (or it's yet another > setting) How do others fare here, dare I ask ? I think the title under which the program is made available to the GUI launcher is determined by the packager of the version you install. It's a bit much to expect the different maintainers to keep track of all the other ways the program can be installed (parallel repositories, flatpak, appimage, local build, ...). So the Kubuntu system in itself has no say over how a program appears in the GUI launcher. > It should be commented (and I will do that) that if you are running > both, they will perhaps look at the same digikam4.db file, and this > could lead to surprises. I keep a backup in case it got mangled, which > it did in my case before I knew about the flatseal permissions I needed, > as I lost whole albums and they would need to be rebuilt! > On the other hand, those installing several versions could be expected to know what they are doing (the more so when they install *beta* versions). It's also important to keep the readme file as short as possible, most won't read long instructions (and a readme that's not read is no better than no readme)... Remco |
In reply to this post by Peter Teuben
I too am having problems with Open With on the flatpak version
I installed the flatpak version of digikam (7.1.0), and both the flatpak and standard version of rawtherapee that's available in the software store (mint v20). Neither show up in digikam anywhere. I can't even go directly to the folder where the .desktop app is for the flatpak. I have flatseal installed and think I have enabled all possible directories. Has anyone figured out how to get other apps to work with this flatpak version? Open With is very broken. -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
Free forum by Nabble | Edit this page |