When a Flatpak app update fails (for example because the installed flatpak client is older than what the app requires, error: "X needs a later flatpak version"), flatpak update on the command line reports this clearly. However, mintUpdate's GUI shows no error at all — the app simply reappears as "update available" on every subsequent check/reboot, with no indication of why the update never applies.
For experienced users this is diagnosable via terminal. For non-technical users (which Mint explicitly targets) this is unsolvable and undermines trust in the update indicator.
Suggested improvement: surface the actual flatpak error/exit reason in the GUI (tooltip, notification, or Update Manager log tab) instead of just re-listing the item as pending.
When a Flatpak app update fails (for example because the installed flatpak client is older than what the app requires, error: "X needs a later flatpak version"), flatpak update on the command line reports this clearly. However, mintUpdate's GUI shows no error at all — the app simply reappears as "update available" on every subsequent check/reboot, with no indication of why the update never applies.
For experienced users this is diagnosable via terminal. For non-technical users (which Mint explicitly targets) this is unsolvable and undermines trust in the update indicator.
Suggested improvement: surface the actual flatpak error/exit reason in the GUI (tooltip, notification, or Update Manager log tab) instead of just re-listing the item as pending.