https://bugs.kde.org/show_bug.cgi?id=523248
Bug ID: 523248
Summary: [Regression] plasma-nm drops WPA passwords and
triggers an authentication loop when KWallet is
disabled, failing to gracefully save system-wide.
Classification: Plasma
Product: plasmashell
Version First 6.7.3
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Networks widget
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
Operating System: Arch Linux (Wayland)
KDE Plasma Version: 6.7.3
Description:
When KWallet is explicitly disabled, the Plasma NetworkManagement applet
currently fails to save new Wi-Fi connection passwords.
Previously, this worked flawlessly: the applet would natively fall back to
saving the connection system-wide via NetworkManager without requiring any
custom Polkit rules, group modifications, or manual intervention. However, in
recent updates, the applet drops the secret entirely if the wallet daemon is
unavailable.
This results in NetworkManager receiving an empty password payload, failing the
initial connection, and spawning the fallback desktop "wifi password" dialog to
request the exact same Wi-Fi password a second time.
Steps to Reproduce:
Disable KWallet globally by creating ~/.config/kwalletrc with:
[Wallet]
Enabled=false
Boot into a Wayland Plasma session.
Click the network applet in the system tray and select a new WPA2/WPA3
Wi-Fi network.
Enter the correct Wi-Fi password into the inline applet prompt and click
Connect.
Observed Behaviour:
The inline prompt accepts the password, but the connection immediately fails. A
secondary fallback window ("wifi password") appears on the desktop demanding
the exact same Wi-Fi password. The applet appears hardcoded to pass secrets to
KWallet, dropping the payload entirely when the wallet is disabled, rather than
natively instructing NetworkManager to save the secret system-wide as it used
to do.
Expected Behaviour:
If local user secrets (KWallet) are disabled or unavailable, plasma-nm should
seamlessly hand the provided password directly to NetworkManager to be saved as
an unencrypted system-wide connection. This native fallback behaviour worked
correctly a few months ago.
Workaround:
Manually forcing NetworkManager to store the secret and ignore user agents
resolves the issue completely. Running sudo nmcli connection modify
"YOUR_WIFI_NAME" wifi-sec.key-mgmt wpa-psk wifi-sec.psk "YOUR_WIFI_PASSWORD"
wifi-sec.psk-flags 0
allows the connection to succeed and entirely bypasses the fallback prompt
loop. No custom Polkit rules or user group modifications are required for this
workaround to succeed.
--
You are receiving this mail because:
You are watching all bug changes.
