NetworkManager plugin NeedSecrets takes time to become operational after wake
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
New
|
Undecided
|
Unassigned | ||
Ubuntu |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
For fully and correctly operational NetworkManager VPN configuration(s) with no unresolved issues, misconfigurations, or connectivity/
After waiting "long enough" (more than a couple of minutes) and then retrying to use a NetworkManager profile with a saved per-user secret, the secret is correctly obtained allowing the connection to be established.
This seems to be dependent on the level of suspend; in my test case, merely hitting the power/suspend button on the device (an HP ZBook G3 Studio), waiting for the screen to go out, then re-waking the device does not trigger this behavior; however closing the lid of the device, letting it go into "full" suspension, then waking it some time later reliably reproduces this issue.
When the issue described presents, the following is logged to the system journal:
Nov 24 12:37:17 ZBook NetworkManager[
With the default configuration, no other messages regarding NeedSecrets are logged to the system journal.
I took care to ensure the network was fully operational before attempting to establish the VPN connection via NetworkManager; full TCP/IP connectivity and DNS resolution was confirmed working before the VPN attempt was made and the NeedSecrets warning was logged.
As mentioned, this has been observed at least since 18.04 and currently against Ubuntu 23.04. The following network-manager packages/versions are installed:
* network-
* network-
* network-
* network-
* network-
* network-
* network-
* network-
* network-
* network-
* network-
* network-
(I should clarify that when I say "since 18.04 and through 23.04" I am not referring to a single installation that has been upgraded; this is referring to multiple clean installations of various versions.)