SUMMARY Flatpak repository priorities are not respected according to the "--prio=" switch. (I initially posted this on discuss.kde.org as I wasn't 100% sure this was a bug, but I got no replies unfortunately, so I've decided to post here.) STEPS TO REPRODUCE ***SEE LINK BELOW FOR STEPS TO REPRODUCE ISSUE OBSERVED RESULT Flatpak orders repositories in the order of; Highest priority system repo to lowest priority system repo THEN highest priority user repo to lowest priority user repo, even if the user repos have been set a higher priority than the system ones. EXPECTED RESULT Flatpak (and discover) orders the configured repositories according to the "--prio=" switch, regardless of whether or not a repository is a user or system repo. The expectation is that the "--prio=" switch is treated as a global option. SOFTWARE/OS VERSIONS Operating System: KDE Linux 2025-09-20 KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.16.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 2 × Intel® Pentium® 3805U @ 1.90GHz Memory: 4 GiB of RAM (3.7 GiB usable) Graphics Processor: Intel® HD Graphics Manufacturer: LENOVO Product Name: 80EW System Version: Lenovo B50-80 ADDITIONAL INFORMATION https://discuss.kde.org/t/flatpak-repo-priorities/40145 I've also searched for any clues on this topic here, but I've not found anything > https://docs.flatpak.org/en/latest/flatpak-command-reference.html
Created attachment 185441 [details] comparison Can confirm they're bit odd. We should also show the name of the remote too. Operating System: Fedora Linux 42 KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.16.8-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600
Hi all, if that's an issue with flatpak priorities handling, shouldn't this be solved on their end and not in Discover?
I guess part of the problem here it's that there's the remote getting added to separate installation. Also several remotes with the same name no less. Please break down the bug not into how you think Discover should be implemented but instead what behaviour you get, what did you expect and why do you think the status quo is wrong. Is it because you've been using this prio setting? Discover follows the priority in the Settings page which predates the prio setting in flatpak. This could be addressed but let's have the whole conversation.