Flatpak updates requiring user confirmation are not handled in GUI (silent failure / refresh loop)
@mtwebster is already working on this.
Since May 20, 2026.
Assessment
This issue has not been assessed yet.
Description
When updating Flatpak applications through the Update Manager in Linux Mint, updates that require user interaction (such as replacement of deprecated apps or runtimes) are not handled correctly.
Instead of prompting the user, the Update Manager:
- silently refreshes the update list
- does not show any progress dialog
- leaves the update pending indefinitely
However, running the same operation via terminal:
flatpak update
correctly prompts the user with:
Replace? [Y/n]:
This indicates that the issue is not with Flatpak itself, but with how the GUI handles interactive prompts.
Expected behavior
When a Flatpak update requires confirmation, the Update Manager should:
- display a graphical dialog explaining the action (e.g., app replacement, EOL runtime)
- allow the user to accept or reject the change
- proceed with the update accordingly
Actual behavior
- No dialog is shown
- No error is displayed
- The update remains stuck
- The user must manually run flatpak update in terminal to proceed
Why this matters
This breaks the “no terminal needed” experience that Linux Mint aims to provide.
Less experienced users may:
- not understand why updates never install
- assume the system is broken
- remain on outdated or unsupported software
Suggested solutions
- Detect when Flatpak returns an interactive prompt and surface it in GUI
- Alternatively, run Flatpak updates with automatic confirmation (-y) and show a summary of changes
- Or display a clear error message directing the user
Additional context
This issue appears especially when:
- applications are deprecated and replaced (e.g. Jellyfin Media Player → Jellyfin Desktop) (this was my case)
- runtimes reach end-of-life
- Dominant language
- Python
- Stars
- 425
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintupdate
-
BUG
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linuxmint/mintupdate#1089 ·
-
BUG
Difficulty 1/5 Under an hour Newbie friendliness 88/100
linuxmint/mintupdate#1062 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
linuxmint/mintupdate#1041 · 1 comment ·
-
FEATURE REQUEST
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#910 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#903 ·
All issues in linuxmint/mintupdate
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100