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

            Bug ID: 528114
           Summary: KSecretD repeatedly prompts to unlock kdewallet during
                    active Fedora session despite successful PAM
                    initialization
    Classification: Frameworks and Libraries
           Product: frameworks-kwallet
      Version First 6.31.0
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

DESCRIPTION

During normal use of Fedora 44 KDE Plasma (Wayland), the KWallet unlock dialog
randomly appears with the message:

"The application 'KDE' has requested to open the wallet 'kdewallet'."

Clicking Cancel causes the dialog to immediately reopen. This repeats
continuously, and I can reproduce the loop simply by repeatedly clicking
Cancel.

I have not changed my Fedora login password or KWallet password. They are
identical.

This appears potentially related to KSecretD and the KDE Secret Service portal.
I have not established which application initiates the original request.

STEPS TO REPRODUCE

1. Log into a Fedora 44 KDE Plasma session.
2. Use the desktop normally. At an unpredictable point, the KWallet unlock
dialog appears.
3. Click Cancel. The dialog immediately reappears, repeatedly.

OBSERVED RESULT

KWallet repeatedly displays an unlock dialog identifying KDE as the requesting
application. Cancelling the dialog does not dismiss it permanently.

The following diagnostic evidence was collected.

PAM initialization:

```text
Oct 31 20:45:51 pam_kwallet5(plasmalogin:session):
    pam_kwallet5: pam_sm_open_session

Oct 31 20:45:51 pam_kwallet_init[1701]:
    final socket path: /run/user/1000/kwallet5.socket
```

The socket exists:

```text
/run/user/1000/kwallet5.socket
```

Later, KSecretD reports:

```text
Oct 31 21:44:56 ksecretd[14108]:
    Lacking a socket, pipe: 0 env: 0

Oct 31 21:44:57 ksecretd[14108]:
    Using kwallet without parent window!
```

The latter message repeats frequently while the unlock prompts occur.

The KDE desktop portal also logs:

```text
Started dbus-:[email protected].
```

An additional KSecretD process (PID 13615) produced these errors:

```text
Created a KConfigGroup on an inaccessible config location "kwalletrc"

error marshalling arguments for create_pool:
dup failed: Too many open files

The Wayland connection experienced a fatal error:
Too many open files
```

The process subsequently exited.

EXPECTED RESULT

KWallet should be unlocked using the credentials provided by PAM during login.
Background Secret Service requests should not cause an endless sequence of
wallet unlock prompts.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.31.0
Qt Version: 6.11.2

ADDITIONAL INFORMATION

Installed packages:

```text
kf6-kwallet-6.31.0-1.fc44.x86_64
kf6-kwallet-libs-6.31.0-1.fc44.x86_64
pam-kwallet-6.7.5-1.fc44
```

KWallet configuration:

```ini
[Wallet]
Close When Idle=false
Enabled=true
First Use=false
Idle Timeout=10
Prompt on Open=false
```

The wallet password matches my Fedora login password.

The KDE portal configuration selects KWallet as the Secret Service backend:

```ini
org.freedesktop.impl.portal.Secret=kwallet
```

A D-Bus capture also showed Secret Portal RetrieveSecret requests from a
Bitwarden Flatpak proxy and the desktop portal. However, terminating Bitwarden
while the repeated prompts were already occurring did not stop them.

Related report:
https://bugs.kde.org/show_bug.cgi?id=524373
https://bugs.kde.org/show_bug.cgi?id=524522
https://bugs.kde.org/show_bug.cgi?id=524522
https://bugs.kde.org/show_bug.cgi?id=526223

That report describes a similar Fedora 44 problem involving PAM socket
initialization and KSecretD being launched without access to the PAM socket. My
installed KWallet version is 6.31.0.

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

Reply via email to