Diagnosing github.com/flathub/org.kde.konsole/issues/55 was made more difficult by how plasmashell’s Task Manager plasmoid appears to prioritise org.kde.flatpak’s .desktop file over konsole-25.12.2-1.fc43.rpm’s, thereby forcing me to invoke $(command -v konsole) in krunner’s F2-produced GUI to invoke it, each time I windowclose’d it. Can I have the Flatpak and RPM packages produce separate .desktop files, and/or prioritise the RPMs?
creating a separate .desktop is a trivial task in the applications editor.
i would start by renaming the default (rpm in your case) native application and giving it a separate icon for easy identification.
then when you install the flatpak that wants that same lane, it will be open as if the native app were not installed.
you could, of course, recreate the native app .desktop, after the fact in much the same way using the editor.
@skyfishgoo, yes, that’s trivial for an application that I shan’t uninstall. However, I frequently uninstall and install Flatpak and RPM packages, and I do so to so many that manually creating .desktop files would be a near-full-time task.
unfortunately, i believe that’s down to the developer of the package in how they name it and what category they tell the installer to place it under.
it’s supposed be automatic so that we don’t have to wade thru tons of install wizard screens like on windows.
i don’t know of any way to preempt that at install time… the programs go where they are told to go and if there’s already something there, it gets replaced.
maybe in the guts of the command line package manager there is a way.
your need to frequently load the same program from different sources sounds like a fine use case for a VM.
@skyfishgoo, I don’t believe that most of that is relevant, because when dolphin applications:/ enumerates the relevant paths defined in $Env:XDG_DATA_DIRS, it could separate those that Flatpak provides, preventing them overriding others’.
I know that rpm -qf /usr/share/applications returns filesystem-3.18-50.fc43.x86_64, so I’d presume that the equivalent for flatpak would be feasible, too. If not, printf '%s\n' "$XDG_DATA_DIRS" | tr ':' '\n' | grep flatpak works!
RokeJulianLockhart@Beedell:~$ printf '%s\n' "$XDG_DATA_DIRS" | tr ':' '\n' | grep -F flatpak
/home/RokeJulianLockhart/.local/share/flatpak/exports/share
/var/lib/flatpak/exports/share
Nah, I just don’t leave that which I don’t need installed. It makes updates take longer.