https://bugs.kde.org/show_bug.cgi?id=527674
Bug ID: 527674
Summary: Discover allows launching stale in-memory instances of
uninstalled native apps when switching to Flatpak
version
Classification: Applications
Product: Discover
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: discover
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Steps to reproduce:
1. Install an application providing a system tray background service (e.g.
Akregator) via system package (APT).
2. Open the app so it minimizes/runs in the system tray.
3. Open Discover and remove/uninstall the system (APT) version.
4. In Discover, switch source to Flathub and install the Flatpak version.
5. Click "Launch" on the Flatpak page in Discover.
Observed result:
Discover does not terminate the obsolete native background process. Instead of
executing the newly installed Flatpak, Discover/D-Bus activates the stale
process remaining in RAM. To the user, it appears as if the Flatpak
installation failed or downgraded to the old version.
Expected result:
1. Discover should either prompt the user that a running background process
needs to be terminated upon uninstallation, OR automatically send a proper
SIGTERM.
2. When the user explicitly clicks "Launch" on a Flatpak entry in Discover,
Discover must execute the containerized Flatpak binary (flatpak run ...), NEVER
foreground a leftover native process.
Why this is critical:
This breaks basic UI predictability. Non-technical users cannot know that a
background daemon is intercepting application launches, leading to severe
confusion and completely broken version migration.
Kubuntu 26.04
--
You are receiving this mail because:
You are watching all bug changes.
