Every few minutes, I see:
I’ve not noticed packet loss. I’m able to connect to the internet. This has been occurring irregularly across different residences, broadband connections, and computer systems, for approximately 2 years.
Not really a Plasma issue - but generally you should try restarting networkmanager ‘systemctl restart Networkmanager’ - something like ❯ systemctl restart NetworkManager.service
You can also completely delete the current connection profile and reconnect.
Next up, look into your DNS Settings - check your router and verify it from other devices.
Connecting to an alternative network might also give some insight (e.g. disconnect from your normal connection, and connect to a phone hotspot).
Finally, you can disable the connectivity checking, look at any firewall or proxy settings you have,
IPv6 can also cause false warnings - you can try ignoring that.
This message appears when Plasma checks connectivity by pinging a server, and the ping fails even if HTTP/HTTPS works.
Some networks can also block ping requests.
2 Likes
I have seen this a while back (maybe 1-2 weeks ago) but not every few minutes, maybe 4-5 times a day.
My assumption back then was that the system occasionally checks availability of a specific server and that server might have had issues
2 Likes
@krake, that’s my estimation too, hence why I mentioned it here. I don’t believe that I see it when booted into Windows 11 24H2.
I should have been more specific. It occurs ⪅ every 20 mins.
@ben2talk, am I correct that a reboot is equivalent? I can’t imagine the service persists across reboots, when even the initialisation service itself is inoperative.
I’ll try your suggestions:
- Disabling Wi-Fi whilst retaining Ethernet.
- The opposite.
- Utilise a different device.
- Utilise a cellular network (extended via a smartphone, acting as an AP).
Uniquely, my gateway, despite being provided by my ISP, and despite including IPv6-capable firmware, isn’t actually capable of negotiating an IPv6 connection with the ISP. I was informed of this by my ISP. Might that be the cause, then?
1 Like
I’m sorry - I’m generally pretty dumb figuring out network issues, I find many avenues but my troubleshooting is mostly down to trial and error.
I wish you luck.
Regards.
1 Like
This doesn’t appear to reproduce with solely Ethernet enabled. Previously, I had Wi-Fi and Ethernet enabled, which would explain the Ethernet symbol in the notification.
I can also now reproduce this on my Framework 16 (laptop) [1] with mostly Category 8 RJ-45 802.3 enabled, alongside 802.11ac-2013, connected to my Teltonika RUTXR1 AP. When I disable .11 from the plasmoid, the error disappears. Is this a bug?
On Fedora, the connectivity check is done by attempting to connect to: http://fedoraproject.org/static/hotspot.txt
(Configured in /usr/lib/NetworkManager/conf.d/20-connectivity-fedora.conf - I got a pointer in the right direction from the Arch wiki.)
Personally I’ve disabled the notification in Notifications >> Application Settings >> Limited Connectivity, as I found it gave me far more false positives (internet connection fine, but Fedora infrastructure down) than true positives. There was one spate of false positives that tipped me over the edge into disabling it, but I can’t remember whether it coincided with your posts back in April.
(I could also have edited the mentioned .conf file to stop the check even being attempted.)
1 Like
@pg-tips, thanks. I’d rather remediate the problem upstream than bypass it, though, since I’d need to do so for so many devices.
This has occurred for maybe 3 years, at this point. I’ll be depressed if the Fedora connectivity check is quite that unreliable.
Do you happen to know what domain is pinged to check? I could set an online service to notify me when it’s 404.
At least on Fedora, I think it’s an HTTP connection, not a ping.
I had an issue at one point (this one was a problem with my ISP) where:
- access to HTTPS resources was fine
- access to HTTP resources failed
- the connectivity check failed and showed an alert in Plasma
So that one was a true positive, although most things appeared fine because most of my browsing is on HTTPS pages.
1 Like
@pg-tips, sorry. Didn’t read it as carefully as I should have.
Since there’s now reason to believe that this might be due to the OS’s configuration of NetworkManager, I’ve posted it at Fedora’s Discourse instance:
1 Like
No worries, the “grammar of hyperlinks” is such that it’s easy to parse it as providing background information, rather than being part of the content of the post!
1 Like