https://bugs.kde.org/show_bug.cgi?id=524122

            Bug ID: 524122
           Summary: Editing Flatpak Settings for an app silently removes
                    user-configured persistent mounts
    Classification: Applications
           Product: systemsettings
      Version First 6.7.80
       Reported In:
          Platform: KDE Linux
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: kcm_app-permissions
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

DESCRIPTION
When editing the settings for an app in the "Flatpak Settings" screen, making
any change to the settings silently removes any persistent mounts that the user
had configured for an app.

STEPS TO REPRODUCE
1. Configure a persistent mount for a Flatpak app, for example `flatpak
override --user org.kde.kcalc --persist=foo`
2. Verify that the persistent mount was indeed applied, e.g. `flatpak override
--show org.kde.kcalc`
3. In System Settings, go to "Application Permissions", select the app, and
click "Manage Flatpak Settings" to open the Flatpak settings for the app.
4. Make any arbitrary permissions change on that screen, and click "Apply"
5. Repeat step 2 (e.g. `flatpak override --show org.kde.kcalc`)

OBSERVED RESULT
The persistent mount has been removed.

EXPECTED RESULT
The persistent mount should have been unaffected.

SOFTWARE/OS VERSIONS
Operating System: KDE Linux 2026-08-09
KDE Plasma Version: 6.7.80
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.1

ADDITIONAL INFORMATION
There is an existing bug (468806) requesting that the Flatpak Settings screen
should show persistent mounts for the app (it currently does not) and allow
tham to be edited.

However this isn't a pure duplicate of that bug. The behaviour described here
(silently removing user-applied settings) is more severe than just not
providing a way of showing and editing the settings.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to