Bug 400928 - after boot, WiFi authorization does not launch kwallet password request on first connect, does on second try
Summary: after boot, WiFi authorization does not launch kwallet password request on fi...
Status: CONFIRMED
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (show other bugs)
Version: 18.08
Platform: Neon Linux
: NOR minor
Target Milestone: ---
Assignee: Valentin Rusu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-10 22:38 UTC by Peter Ped Helcmanovsky
Modified: 2024-07-09 18:37 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
journalctl -u NetworkManager sanitized log (2.19 KB, text/x-log)
2018-11-10 22:38 UTC, Peter Ped Helcmanovsky
Details
journalctl -u Networkmanager -u wpa_supplicant log (19.05 KB, text/x-log)
2019-02-03 16:47 UTC, alexkde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Ped Helcmanovsky 2018-11-10 22:38:42 UTC
Created attachment 116241 [details]
journalctl -u NetworkManager sanitized log

SUMMARY

Some WiFi networks after reboot will have to fail first try to connect to open KWallet password prompt on second try.
(started to happen recently, last couple of weeks, I think last two or max three KDE updates, 5.13+ probably).


STEPS TO REPRODUCE
1. reboot, log into plasma (my KWallet is using different password than user, so it is not opened yet)
2. network manager will try to connect to known+preferred WiFi network

OBSERVED RESULT

A) At home network there's about 30s period of trying to authenticate the WiFi network, then it fails, and network manager will try second time.

That immediately does launch KWallet password prompt window, after entering password the network password is retrieved and connection established.


B) At office network the KWallet password window is launched immediately, after entering the KWallet password the network password is retrieved and connection established (on first try).


It does connect to WiFi without problem after awakening from sleep, or after unlocking plasma. Only after full reboot (didn't try logout yet, actually, maybe I should) the first try fails.


The distinction office/home WiFi is reliable, although from the network manager setting window the difference between networks is not visible, except different SSID (same type "WPA/WPA2 personal" security and both passwords are stored in KWallet in the same way, available only to my user ... may be the response time of router is different, but not perceivable in human time resolution).

EXPECTED RESULT

KWallet password prompt launched as soon as network manager needs password for WiFi (retrieving it already at first try), without ~30s delay.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon User Edition 5.14 x86_64
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2
Kernel: 4.18.16-041816-generic
kwalletmanager package version: 4:18.08.3-0xneon+18.04+bionic+build11

ADDITIONAL INFORMATION

I'm adding from `journalctl -u NetworkManager` the part of log around first try failure, followed by successful connect on second try.
Comment 1 Aranjedeath 2018-12-23 03:58:01 UTC
I can confirm this issue -- however my kwallet is either passwordless or it's the same as my user (I don't ever remember configuring it, so I don't know which). Either way, same experience as section A) of Peter's post. 

Mine times out 30s after boot with "no secrets provided", and then instantly connects to whichever WiFi I am near. 

A difference, however, is that mine does not reconnect to any WiFi after it sleeps. It sends the same error -- no secrets provided, but just stops at that point. turning WiFi on/off in KDE does not fix or reset. I have to reboot after to restore wifi.
Comment 2 alexkde 2019-02-03 16:44:12 UTC
I can confirm this bug report on Manjaro with KDE Plasma 5.14.5:

After a reboot, the networkmanager tries to connect and authenticate to the WiFi for about 30s, disconnects then and finally immediately connects.

In contrast to the OT both the KWallet and the user password are identical.

Last but not least I attach a sanitized but otherwise complete log 
> $ journalctl -u NetworkManager -u wpa_supplicant
to this comment.
Comment 3 alexkde 2019-02-03 16:47:31 UTC
Created attachment 117809 [details]
journalctl -u Networkmanager -u wpa_supplicant log
Comment 4 Txutxifel 2019-04-29 14:49:42 UTC
Hi
Same here, with Opensuse Tumbleweed Updated (KDE Plasma 5.14.5). It does IMAP account (Gmail) to start always disconnected in every login.

My temporaly "fix" is saving wifis password (un-encrypted) for all users (NetworkManager option). It does no connecting delays and kmail is always sync in login.

Cheers
Comment 5 Márton Lente 2023-04-08 09:14:52 UTC
Hello,

I can confirm the above bug still is present on KDE Plasma 5.27.3 running on openSUSE Tumbleweed 20230403.

When logging in to a user account, KDE Daemon asks for a known Wi-Fi networks's password, even though it's present in KWalllet. By simply closing KDE Daemon window, and manually connnecting to the known Wi-Fi network from the taskbar works though, without re-entering Wi-Fi password.

It seems that the Wi-Fi password is asked before KWallet could initialize. (My KWallet is set up to not have password, so that the password storage is opened right after logging in.)

Best,
Márton Lente
Comment 6 Tristan Miller 2024-07-09 18:37:24 UTC
Still reproducible with Plasma 5.27.9 on openSUSE Leap 15.5.