Bug 412398

Summary: No longer auto-reconnects to wireless network after waking from sleep
Product: [Plasma] plasmashell Reporter: Nate Graham <nate>
Component: Networking in generalAssignee: Jan Grulich <jgrulich>
Status: RESOLVED UPSTREAM    
Severity: major CC: jgrulich
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
URL: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/256
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Networkmanager log

Description Nate Graham 2019-09-27 13:21:29 UTC
I have plasma-nm and all other KDE software built from git master. This regression appeared a few days ago.

STEPS TO REPRODUCE
1. Close my laptop's lid
2. Open it and unlock the screenlocker

OBSERVED RESULT
Plasma-nm does not automatically reconnect to my wifi network

EXPECTED RESULT
It does auto-reconnect.

ADDITIONAL INFORMATION
Nothing changed about my wifi network, Qt version, Kernel, or non-KDE software, so I have to assume that this is a plasma-nm regression.
Comment 1 Jan Grulich 2019-09-27 14:32:15 UTC
Check if you have "autoconnect" set in your configuration of your network. If you have, then it's most likely an issue in NetworkManager / drivers, because we don't control autoconnection.
Comment 2 Nate Graham 2019-09-27 16:58:56 UTC
Yes, auto-connection is on with priority 0.

If this means it's an upstream issue, where should I start looking?
Comment 3 Jan Grulich 2019-09-27 17:05:22 UTC
1) Check NetworkManager log if there is anything mentioned
2) Check for your recent distro updates if there were updated of NetworkManager or kernel or anything possibly related

There wasn't any change in plasma-nm recently which would break this behavior.
Comment 4 Nate Graham 2019-09-27 23:43:05 UTC
Created attachment 122912 [details]
Networkmanager log

I'm attaching the networkmanager log showing the state changes before and after sleeping and waking the machine (at which point plasma-nm has disconnected from the network and not re-connected to it). I'm not really an expert in interpreting the log; maybe something stands out to you? And I'm sorry for abusing Bugzilla to ask for you help on this. If there's a more appropriate forum, direct me there and I'll close this bug.
Comment 5 Jan Grulich 2019-10-01 13:55:14 UTC
From the log I just see that the device gets to "disconnected" state, but I don't understand the reason.

You can report your issue here: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
Comment 6 Nate Graham 2019-10-02 20:51:12 UTC
Thanks for your help. I have filed an upstream issue: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/256
Comment 7 Ben Cooksley 2024-12-23 18:23:36 UTC
Bulk transfer as requested in T17796