Bug 451139

Summary:	NetworkManager 1.36.0, Network manager does not automatically reconnect to known network after reset
Product:	[Plasma] plasma-nm	Reporter:	NIk <nik.kaiser87>
Component:	general	Assignee:	Jan Grulich <jgrulich>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	aronkvh, daniele.doehle, nate
Priority:	NOR	Keywords:	regression
Version:	5.24.2
Target Milestone:	---
Platform:	Other
OS:	Linux
URL:	https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/947
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	NM applet showing wrong "last connected" time

Description NIk 2022-03-04 20:28:40 UTC

Created attachment 147282 [details]
NM applet showing wrong "last connected" time

SUMMARY
Since 5.24.2 including this commit https://invent.kde.org/plasma/plasma-nm/-/commit/622f53da6184dc90d5834a9e75fb1cb1c3af5986, Network Manager does not reconnect to my known, wired network connection, if it is being reset from the outside (for example a router reset). 
It did automatically reconnect in 5.24.1 and .0. The connection is set to "connect autmatically". I do not have any other connections saved/available in NM. 


STEPS TO REPRODUCE
1. Connect to (wired) network, for example a router
2. Cut the power on the router and plug it back in
3. After router has booted up, observe NM is not reconnecting automatically

OBSERVED RESULT
NM is not reconnecting automatically

EXPECTED RESULT
NM should reconnect automatically, if the network is saved and known


Operating System: openSUSE Tumbleweed 20220302
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.11-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × 11th Gen Intel® Core™ i5-11600K @ 3.90GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics

ADDITIONAL INFORMATION
Included picture shows the state after the router has been restarted and is booted up. NM shows my connection as "used last two hours ago" which isnt true, its rather 2 minutes. Maybe this is part of the bug. If I click connect it does connect normally.

Comment 1 NIk 2022-03-04 20:53:11 UTC

More info: In the moment of the reset of the connection, it seems that another connection is being created by NM (enp3s0), whereas my normal connection is "Kabelgebunden" (meaning wired).
Upon finished restart of the router (or if you put the network plug back in), it stays connected to this new non functional enp3s0 thing, whatever that is, saying it has "limited connectivity". The actually working wired connection gets ignored. 
If I connect manually to said wired connection, the enp3s0 thing disappears.

This is all very weird, here is a screenshot of mentioned state: https://imgur.com/a/W9bvObB

Lets not needlessly fiddle around with all NM/network-related things, its too important :)

Comment 2 Nate Graham 2022-03-22 02:42:34 UTC

Darn, I will investigate.

Comment 3 NIk 2022-03-22 04:17:43 UTC

(In reply to Nate Graham from comment #2)
> Darn, I will investigate.

Tip: It has something to do with this: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/947

I talked to an OpenSuse dev/maintainer, and we went down the rabbit hole together a bit. 
If mentioned error, is it correct that it's not a KDE issue?

Comment 4 Nate Graham 2022-04-10 16:05:46 UTC

Indeed, looks like the timing is a coincidence and the root cause is that regression in networkmanager itself.

Comment 5 Nate Graham 2022-04-10 16:05:54 UTC

*** Bug 447577 has been marked as a duplicate of this bug. ***

Comment 6 Nate Graham 2022-04-10 16:06:18 UTC

*** Bug 452355 has been marked as a duplicate of this bug. ***

Comment 7 Nataniel 2022-06-28 13:36:20 UTC

*** Bug 435269 has been marked as a duplicate of this bug. ***