Bug 501287 - When detecting a limited/non-existent connectivity situation, check for restored connectivity more quickly
Summary: When detecting a limited/non-existent connectivity situation, check for resto...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networks widget (other bugs)
Version First Reported In: 6.3.2
Platform: Neon Linux
: LO minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2025-03-10 09:25 UTC by Martin Tlustos
Modified: 2025-03-19 22:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Tlustos 2025-03-10 09:25:24 UTC
Often (maybe always), the wifi widget in the notification area shows limited connection at startup, which is not true. Disconnecting and reconnecting fixes it.

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Boot kde in an environment with a know wifi connection
2. 
3. 

OBSERVED RESULT
The wifi widget shows that the automatically established connection has limited connectivity

EXPECTED RESULT
It should show the accurate information that the connection works without problems (which it does).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 TraceyC 2025-03-10 16:49:29 UTC
Thanks for the report. We need additional detail in order to investigate the problem. Thanks.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version:
Comment 2 Martin Tlustos 2025-03-12 11:59:52 UTC
Operating System: KDE neon 6.3
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-19-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor 1: AMD Radeon Graphics
Graphics Processor 2: AMD Radeon 550X Series
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12
Comment 3 cwo 2025-03-12 14:17:10 UTC
Do you use a VPN?
Comment 4 Nate Graham 2025-03-12 18:12:27 UTC
.
Comment 5 Martin Tlustos 2025-03-13 08:20:22 UTC
No. But the wifi connection is weak, as there are two walls in between. So this only happens if the wifi signal is weak.
Comment 6 Nate Graham 2025-03-13 18:16:49 UTC
Is the signal weak enough to make your internet connectivity very slow?
Comment 7 Martin Tlustos 2025-03-14 08:04:20 UTC
Well, I can't really tell, as I often work in Africa where the internet is REALLY slow, so compared to that - no. But compared to normal internet in the west, it might... ;-)
Comment 8 Nate Graham 2025-03-14 15:22:41 UTC
Hmm, it's possible that it's got periods of slowness that are so slow that they trip the "limited connectivity" detection.
Comment 9 Martin Tlustos 2025-03-19 06:56:04 UTC
Likely. It does have periods where the internet is non-responsive at least for a couple of seconds. If something like this would happen at startup, it could trigger the limited connection warning.
Comment 10 Martin Tlustos 2025-03-19 06:56:54 UTC
And it does not always appear, only sometimes, which also supports the above assumption.
Comment 11 Nate Graham 2025-03-19 14:09:38 UTC
In that case... it seems like the widget is working properly?
Comment 12 Martin Tlustos 2025-03-19 17:01:27 UTC
It depends on what you see as properly. If the internet works, but the widget shows limited connectivity, I think it's misleading. Also, after disconnecting and reconnecting, it shows normal connectivity. Maybe it doesn't check often enough to see that connectivity is restored?
Comment 13 Nate Graham 2025-03-19 22:37:28 UTC
Well you did say "It does have periods where the internet is non-responsive at least for a couple of seconds". So it sounds like the widget managed to be checking for connectivity during a moment when that happened.

So everything is working as intended here. We could perhaps improve the UX by reducing the polling interval so it's a bit quicker to detect when connectivity has been restored.