I have VLC installed from both Extra repo (installed as a dependency for another package by KDE) and Flatpak.
The Flatpak version is my daily use version, and has customised preference.
Hence, both versions can be differentiated visually. Both versions can be launched side by side with no issue.
MakeMKV (AUR vs. Flatpak)
Similarly, I also have MakeMKV from AUR and Flatpak.
Again, both versions can be launched side by side with no issue.
MKVToolNix GUI (Extra repo vs. Flatpak)
Now, the latest version of MKVToolNix GUI is 90.0 (Flatpak) and 89.0.3 (Extra repo).
I have both version installed.
However, unlike VLC and MakeMKV (each, respectively, has 2 icons appeared in App Launcher, corresponding to each version), only 1 icon appears in App Launcher, and it launches Flatpak version.
So, I launched Pamac, searched for MKVToolNix, selected the Extra repo version, and clicked “Launch”.
And… the Flatpak version launched!
So, is this the expected behaviour?
In this scenario, how should one launch the MKVToolNix GUI (Extra repo version)?
When an app doesn’t appear in App Launcher, I can only think of finding the app in Pamac, and launch it there.
Pardon me for my limited knowledge on Linux…
Sorry - no offense was intended.
I do not use Flatpaks, have zero experience with them and how they are (supposed to be) integrated in the system and system menu to start them.
I only have a few AppImages which I launch via the command line.
Is such behaviour (MKVToolNix GUI scenario) considered a common practice?
Or somehow along the development, there comes a bug?
App from extra repo or AUR, often encounter dependency conflict when updating the system.
I’m not well verse to troubleshoot and resolve the bugs.
So the only approach I can think of, is to use Flatpak, where everything (that works) is packed as whole package.
App from extra repo should never produce issues - there may be an occasional replace or consolidation you need to handle - but that is it.
AUR on the other hand is usually build from source and requires attention on updating the system because an AUR app may depend on the very libraries you are updating.
Flatpak is installed and run using flatpak commands and the apps are stored in /var/lib/flatpak
flatpak install command may - depending on the actual app installed - provide some means of interacting with the system.
Example for firefox
flatpak install firefox
When installation is done
flatpak run org.mozilla.firefox
There may be certain degrees of desktop integration - usually provided through an appropriate xdg-desktop-portal-<env> package
That is the nature of Manjaro (stable) - should not happen as often or at all when on unstable branch.
From what I know, the same is true for AppImages - but these are not always available.
I run ClipGrab.AppImage - it’s the only one I have.
Can’t help with Flatpaks.
$ pamac search -f /usr/share/applications/org.bunkus.mkvtoolnix-gui.desktop
/usr/share/applications/org.bunkus.mkvtoolnix-gui.desktop is owned by mkvtoolnix-gui
