Did You rebooted after disabling it?
1 Like
Yes I rebooted. I can't tell if it did anything. The failed to connect notification is still popping up.
Maybe its just some low level bug in the OS. Another user linked some threads for me to read, and in one a guy with a new laptop was experiencing the same issue. Unfortunately he didn't get a solution. The difference between that guy and me is he connected with a mediatek wifi card, and my connection is through Realtek ethernet.
1 Like
Could You post the Output of sudo lshw -C network please? This shown Infos about Your Network Hardware Stuff.
Here you go:
*-network
description: Ethernet interface
product: Ethernet Controller I225-LM
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:0f:00.0
logical name: enp15s0
version: 03
serial: 20:3a:43:04:5f:43
size: 1Gbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=igc driverversion=7.0.0-28-generic duplex=full firmware=1057:8754 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:24 memory:a0000000-a00fffff memory:a0200000-a0203fff memory:a0100000-a01fffff
*-network
description: Ethernet interface
product: Realtek Semiconductor Co., Ltd.
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:10:00.0
logical name: enp16s0
version: 01
serial: 34:5a:60:d7:43:1a
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=7.0.0-28-generic duplex=full firmware=rtl8126a-3_0.0.5 08/30/24 ip=192.168.1.19 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:41 ioport:d000(size=256) memory:a0300000-a030ffff memory:a0310000-a0313fff
Okay, that should be fine. I see, You are on Kernel 7.0. You could try to switch to the older 6.17 Kernel and check if it works right again. To do that, choose on Startup on the GRUB Menu ''Advanced Options'' and there the Option with the 6.17 Kernel (without Recovery Mode).
The command just searches the network protocol file for strings error fail and reject:
journalctl -u NetworkManager.service | grep -i "error|fail|reject"
That the command shows no output at all means only that in the network protocol is nothing pointing to an error, fail or reject. But the system doesn't tell you that: you just see that nothing found what you searched for.
We can have an other look into the network protokoll:
journalctl -u NetworkManager.service --since "24 hours ago"
OK. Here it is ...
andym@andym-MS-7E70:~$ journalctl -u NetworkManager.service --since "24 hours ago"
Aug 02 10:25:36 andym-MS-7E70 systemd[1]: Starting NetworkManager.service - Net>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9081] N>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9082] R>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9113] m>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9113] m>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9187] h>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9187] h>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9191] d>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9197] m>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9197] m>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9219] L>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9232] L>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9235] L>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9242] L>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9246] L>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9247] m>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9248] m>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9248] m>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9253] s>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9254] s>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9254] i>
Aug 02 10:25:36 andym-MS-7E70 NetworkManager[1060]: [1785662736.9255] i>
Aug 02 10:25:37 andym-MS-7E70 generate[1284]: Permissions for /lib/netplan/00-n>
lines 1-23
Thanks. It's just an annoyance to be fair. The notification keeps coming, but I've never had any network issues at all 
In this LinuxMint thread is also shown a solution:
https://forums.linuxmint.com/viewtopic.php?t=452005
Perhaps it would work in gnome, too.
As the output of journalctl is missing the status, it is usually redirected and stored within /var/log/syslog.
Let`s see if there we can find any errors, fails or rejects:
grep -iE "error|fail|reject" /var/log/syslog | grep NetworkManager
Please give us the output of the whole line length without cutting it.
Totally understandable.