[frameworks-kwallet] [Bug 523878] New: Secret Service session missing after login causes Chromium/Flatpak applications to lose access to stored login session

[email protected] Wed, 05 Aug 2026 06:09:46 +0000
Newsgroups gmane.comp.kde.devel.bugs
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=523878

            Bug ID: 523878
           Summary: Secret Service session missing after login causes
                    Chromium/Flatpak applications to lose access to stored
                    login session
    Classification: Frameworks and Libraries
           Product: frameworks-kwallet
      Version First 6.26.0
       Reported In:
          Platform: Other
                OS: Other
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

After logging into KDE Plasma, several Chromium/Electron-based applications
could no longer access their previously stored login sessions.

I had to authenticate again in Mailspring and in a browser session connected to
Vaultwarden.

This occurred once so far, on 2026-08-01. I cannot yet provide reliable
reproduction steps.

System information:

* Operating System: Bazzite 44
* Deployment: bazzite-nvidia-open stable-44.20260515
* KDE Plasma: 6.6.4
* KDE Frameworks: 6.26.0
* Qt: 6.10.3
* Kernel: 6.19.14-ogc5.1.fc44.x86_64
* Session: Wayland
* GPU: NVIDIA GeForce RTX 4080 SUPER

Relevant log sequence:

```text
Aug 01 10:59:18 plasmalogin-helper[2757]:
pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket

Aug 01 10:59:20 systemd[2720]:
Started plasma-kwallet-pam.service - Unlock kwallet from pam credentials.

Aug 01 10:59:20 pam_kwallet_init[3110]:
socat W address is opened in read-write mode but only supports read-only

Aug 01 10:59:23 ksecretd[2759]:
Failed to register with host portal
QDBusError("org.freedesktop.portal.Error.Failed",
"Could not register app ID: Connection already associated with an application
ID")

Aug 01 10:59:32 systemd[2720]:
Started dbus-:[email protected].

Aug 01 10:59:32 kwalletd6[4208]:
g_dbus_proxy_get_object_path: assertion 'G_IS_DBUS_PROXY (proxy)' failed

Aug 01 10:59:32 kwalletd6[4208]:
Failed to register with host portal
QDBusError("org.freedesktop.portal.Error.Failed",
"Could not register app ID: App info not found for 'org.kde.kwalletd'")

Aug 01 10:59:32 kwalletd6[4208]:
"Can't find session /org/freedesktop/secrets/session/1"

Aug 01 11:00:04 flatpak[5100]:
Existing KWallet password is empty. Generating a new one.

Aug 01 11:00:04 kwalletd6[4208]:
"Can't find session /org/freedesktop/secrets/session/1"

Aug 01 11:00:04 flatpak[5100]:
KWallet writePassword failed with code: -1
```

The same errors occurred again at 11:10:

```text
Existing KWallet password is empty. Generating a new one.
Can't find session /org/freedesktop/secrets/session/1
KWallet writePassword failed with code: -1
```

Both wallet-related processes were running after login:

```text
/usr/bin/ksecretd --pam-login 13 14
/usr/bin/kwalletd6
```

Installed package versions:

```text
kf5-kwallet-5.116.0-5.fc44.x86_64
kf5-kwallet-libs-5.116.0-5.fc44.x86_64
kf6-kwallet-6.26.0-1.fc44.x86_64
kf6-kwallet-libs-6.26.0-1.fc44.x86_64
kwalletmanager5-26.04.0-1.fc44.x86_64
pam-kwallet-6.6.4-1.fc44.x86_64
signon-kwallet-extension-26.04.0-1.fc44.x86_64
xdg-desktop-portal-1.21.1-1.fc44.x86_64
xdg-desktop-portal-gtk-1.15.3-3.fc44.x86_64
xdg-desktop-portal-kde-6.6.4-1.fc44.x86_64
```

The wallet configuration was not deliberately changed, disabled or reset. The
applications worked again after I entered their login credentials.

Actual result:

Applications received an empty or unavailable password-store value and lost
access to existing encrypted login sessions.

Expected result:

The Secret Service and KWallet session should be initialized consistently after
login. Applications must retain access to previously stored cookies,
authentication tokens and other encrypted session data.

Related report:

Bug 509680 was initially suspected because some symptoms and involved
components appear similar. However, I was asked to open a new report because
the root cause may be different.

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