Bug 411848

Summary: captive portal detection not refreshing
Product: [Plasma] plasmashell Reporter: Harald Sitter <sitter>
Component: Networking in generalAssignee: Jan Grulich <jgrulich>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Harald Sitter 2019-09-12 09:18:49 UTC 
captive portal detection currently is only refreshed through nm (based on a timer) this means that even after having unlocked a portal the connection icon of the applet will show limited connectivity until the timer based refresh occurs. it'd be grand if plasma-nm forced a refresh after having done the unlock. very tricky to implement of course

STEPS TO REPRODUCE
1. be behind portal
2. have nm properly set up to detect limited connectivity
3. get notification upon connecting
4. click login
5. login

OBSERVED RESULT
icon stays in limited mode for quite a while by default, lowering the timeout wouldn't be good either because then we spam the network with needless probe events

EXPECTED RESULT
icon updates very soon

COMMENT
possible solutions:
- use a qwebengineview to render the login page (with a button to go to browser just in case), when the view is closed redo the portal check... + also needs a way to say "use as is" to disable the login checks

- check if browsers can be operated in a similar fashion to a standalone view (i.e. standalone minimal window, when closed refresh state)

- make a crappy hack where the login page is embedded in a local page which somehow tracks and communicates with plasma-nm
Comment 1 Ben Cooksley 2024-12-23 18:23:47 UTC 
Bulk transfer as requested in T17796
Comment 2 Nate Graham 2025-08-06 22:24:22 UTC 
I haven't seen this happen in ages; the "limited connectivity" messages goes away very quickly now. Is it still a problem for you?
Comment 3 Bug Janitor Service 2025-08-21 03:47:00 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2025-09-05 03:48:21 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.