[Bug]: Flatpak page shows flathub/stable for an app installed from flathub-beta (PrusaSlicer: 2.9.7 offered, 3.0.0 installed)

Open Beginner friendly
#144 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp, linux
Domain
desktop

Research direction

Start in src/flatpakclient.cpp at preferred() (lines 49-56), which ranks catalogue entries flathub-first, then stable. Check how toItem() merges the chosen catalogue entry with the installed ref, and where installedRefs is built, since the suggested fix depends on it. Done means an installed beta ref shows its own remote and branch, and uninstalled apps still prefer flathub/stable. Confirm the expected behaviour (match the installed ref, or list both) with the maintainer first.

Written by the indexing model from the issue text.

Description

Summary

The Flatpak page offers the wrong copy of an app when the installed copy comes from a different remote or branch than the one the catalogue dedupe prefers. PrusaSlicer is installed from flathub-beta / branch beta, version 3.0.0, but the page shows flathub / branch stable, version 2.9.7 as the app's version, with "installed from flathub-beta".

Environment

  • CachyOS rolling, KDE Plasma 6.8.3 / KWin Wayland
  • cachyos-packageinstaller 2.0.0-1
  • flatpak 1.18.4
  • Remotes: flathub (system), flathub-beta (system), flathub (user)

Steps to reproduce

  1. flatpak install flathub-beta com.prusa3d.PrusaSlicer (installs branch beta, version 3.0.0)
  2. Open the Package Installer, go to the Flatpak page, search for PrusaSlicer.
  3. The page reports 2.9.7 as the available version and the installed version as 3.0.0.

What the system reports

$ flatpak list --app --columns=application,branch,installation,origin,version
com.prusa3d.PrusaSlicer    beta    system    flathub-beta    3.0.0

$ flatpak remote-ls --system flathub --app --columns=application,branch,version
com.prusa3d.PrusaSlicer    stable    2.9.7

$ flatpak remote-ls --system flathub-beta --app --columns=application,branch,version
com.prusa3d.PrusaSlicer    beta      3.0.0

Cause

src/flatpakclient.cpp, preferred() (lines 49-56):

/// Which of two offers of the same app is shown: Flathub before other remotes, the stable
/// branch before others, then by name so the choice never depends on the order of loading.
bool preferred(const FlatpakApp& a, const FlatpakApp& b) {
    const auto rank = [](const FlatpakApp& app) {
        return std::tuple(app.remote != "flathub"_L1, app.branch != "stable"_L1, app.remote, app.branch);
    };
    return rank(a) < rank(b);
}

The catalogue of every system remote is loaded and deduplicated per app id with preferred(), so the flathub/stable entry always wins — even when the installed ref is on another remote and branch. toItem() then mixes that entry with the installed copy: title and available version come from flathub/stable (2.9.7), while installedVersion, installedFrom and branch come from the installed beta copy.

The same ranking ignores the user installation, which is fine for the catalogue (the README says only system catalogs are read) but means an installed beta ref has no way to win.

Expected

When an app is installed, the offer should be the catalogue entry that matches the installed ref (same remote and branch) — or, if the catalogues disagree, both should be listed. Only uninstalled apps should fall back to "flathub, then stable".

Suggested fix

Rank by whether the ref is installed before the flathub/stable heuristics:

const auto rank = [&](const FlatpakApp& app) {
    const bool isInstalled = std::ranges::any_of(installedRefs, [&](const auto& ref) { return ref == app.ref; });
    return std::tuple(!isInstalled, app.remote != "flathub"_L1, app.branch != "stable"_L1, app.remote, app.branch);
};

Impact

The version shown for such an app is wrong, and the install/update action on that page targets the stable copy instead of the one the user is tracking. Updates themselves come from flatpak remote-ls --updates, so the update list is not affected — only the app offer and its displayed version.

Dominant language
C++
Stars
43
Forks
39
Avg merge
1d 6h
Merged PRs (30d)
12

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CachyOS/packageinstaller

All issues in CachyOS/packageinstaller

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.