br1anstorm wrote: ⤴Wed Jan 18, 2023 10:12 am
- apparently Flatpak (or Flathub) is now "built into" Mint from version 21 onwards (and presumably now also into LMDE5?), which seems to be the reason why the Update Manager pushes out Flatpak updates which are sometime both numerous and bulky. Why is this now built in or forced on to all Mint users, even those like me who actually don't want to use Flatpaks? (I might add that on my other laptop, running Mint 19.1, there is no Flatpak at all in /var/lib).
Linux Mint has supported flatpak for over 5 years now, since Linux Mint 18.3:
https://web.archive.org/web/20210804225 ... atsnew.php. Since then the Software Manager has been able to install flatpaks from the Flathub remote out-of-the-box.
With Linux Mint 20.2 the controls for automatically updating flatpaks moved into Update Manager:
https://www.linuxmint.com/rel_uma_cinnamon_whatsnew.php. And with Linux Mint 21.1 Update Manager now can show individual flatpak updates and let the user selectively install them:
https://www.linuxmint.com/rel_vera_cinn ... atsnew.php. Several smaller improvements were done in intermediate releases.
Everything that's new in Linux Mint 21.1 has been rolled out to LMDE hence you have this added functionality now as well. That Update Manager shows you flatpak updates and lets you selectively install them only changes the visibility of updates. You have been able to install flatpaks through Software Manager for over 5 years. It is not something new.
br1anstorm wrote: ⤴Wed Jan 18, 2023 10:12 am
- there are real concerns over security loopholes in Flatpak. See the details at
https://www.flatkill.org/ . I don't understand the technicalities, but it doesn't look good.
See rene's answer for what I think about that website.
You can view and change the sandbox configuration of flatpaks with Flatseal — and it is much nicer than other sandboxing solutions in that regard. I have a dozen or so flatpak apps installed. Some allow filesystem=host (and logically so, for a file manager for example) but more only filesystem=home or even more limited to one or a few specific directories in my home directory. You can easily restrict an app to more limited access if you want to.
From Linux Mint's perspective flatpaks are supplementary to the official repositories; you can get additional apps or the latest releases of apps from there. You don't need to use it but you can if you have a use for it. By adding some additional remotes (flathub-beta, gnome nightly, kde nightly) you can also get development versions which is very useful to make good bug reports for apps — because you can test your issue with a version directly supported by the app developers.
br1anstorm wrote: ⤴Wed Jan 18, 2023 10:12 am
So I went looking. Here's what I found....
$ flatpak list
<cut for brevity>
I have no idea what Mesa is or what it does. It also looks as if some of the features which I had regarded as integral parts of the Mint OS rather than optional add-on apps - like the Mint-Y themes - are packaged as Flatpaks.
And the real eye-opener: I seem to have a Flatpak that relates to KDE software apps. I know that KDE tends to be bulky. And I'm a disciple of @Pjotr, whose wise advice is that it's not a good idea to mix different DEs and their software. I would therefore stay away from trying to install KDE apps (like K3b) anyway. So what's going on here? Why have I got KDE-related Flatpak stuff already on my system, and am now being offered a large (657MB) update to it?
Instead, use
flatpak list --app
to just see which apps you have installed as flatpak. It will only show nomacs I think; the rest are runtimes that are used by that app. The Mint themes are added so that your flatpak apps look native on Linux Mint. Flatpak apps can't use themes from the host OS but they can use the same theme if it is installed as a flatpak runtime.
The KDE runtime is installed because nomacs is a KDE app, as rene answered. The rest of the runtimes are graphics APIs, like Mesa:
https://en.wikipedia.org/wiki/Mesa_(computer_graphics). Installed because nomacs or the KDE runtime requires them. Flatpak runtimes like these make it so that different apps — while still sandboxed and isolated from the host OS — can share libraries so they only need to be downloaded once and not for each app that uses them.
And as answered elsewhere, flatpak can't tell you exactly how big an install or update is but it can say how large it will be at most. Which is why Update Manager shows it with "<" (less than). flatpak uses ostree for file management and that makes it so that when installing something new or updating something, only new and changed file parts need to be download. Many files may stay the same between versions and thus when updating these won't need to be downloaded again. So usually the actual update is (much) smaller than the maximum shown.
br1anstorm wrote: ⤴Wed Jan 18, 2023 10:12 am
If I purge or get rid of all this (and there seem to be different ways of doing so) what, if anything, will fall over? I can do without the nomacs app. But what will be the consequences for my Mint-Y theme(s), for example? And what if I remove the Mesa, Intel, openh264 Flatpaks?
No, the whole point of flatpak is that your OS
won't fall over regardless of what you do with your flatpak apps. So go ahead and run:
flatpak uninstall --delete-data nomacs
And then:
flatpak uninstall --delete-data --unused
And that should remove all flatpaks.
You can additionally remove the Flathub remote if you don't want to install flatpaks:
flatpak remote-delete flathub
br1anstorm wrote: ⤴Wed Jan 18, 2023 10:12 am
Is Mint at risk of becoming too complex, or too bloated, for its own good?
All that has changed since flatpak support was added over 5 years ago is that since a short while ago flatpak updates are visible in Update Manager. Maybe that is too much complexity visually, but that is all it is.
Personally I don't need control at this level: flatpak updates can't break the OS so I don't need to care about them. So I've them to install automatically.