Used a hotspot at a hotel and got a nice login, works great. Since using the computer after that, the hotspot login screen randomly pops up, even when having a connection to the internet. Sometimes over playing video, sometimes fullscreen on an externally attached screen. I noticed : https://forums.fedoraforum.org/showthread.php?315106-Random-pop-up-of-gnome-hotspot-login-screen (old but seems same issue) and https://www.reddit.com/r/Fedora/comments/13apn2t/random_hotspot_login_popup/ where someone writes : touch /etc/NetworkManager/conf.d/20-connectivity-fedora.conf That seems to disable the hotspot login screen, which is not what I want, I would like it to pop up if I actually connect to a network requiring login / confirmation as many do these days. Reproducible: Always Steps to Reproduce: 1. Connect to an access point to triggers hotspot ( not sure if needed ) 2. Use computer 3. Be surprised by occasional screen flash, hotspot loging screen Actual Results: Have the hotspot login screen pop up when required by network and not randomly otherwise. Expected Results: random pop ups I think this is important to fix because it seems a bit like one gets hacked, not a nice experience.
Looks like I mixed up the expected and observed behaviour. To clarify, the expected behavior is that the hotspot login works on networks that need it and that besides that, not random pop ups occur.
Another "trigger" to this that I found was connecting to a VPN. In my case I have been using a VPN for a few days with no problem, but then the hotspot login window started to pop up a day ago. I haven't used a hotspot login yet on Fedora after updating, so a VPN connection may also be another trigger. There are one or two reports from the same Reddit post linked above about a Nginx error: https://imgur.com/a/6mPh9w7 , and this also makes one feel they have been hacked with such a warning.
More people complain here: https://discussion.fedoraproject.org/t/hotspot-popup-window/82237
I keep getting bugged by this bug for info. Can anyone explain what is needed? I don't see how I can change the red options. Anyone who can, please do so. thanks.
(In reply to Vincent Gerris from comment #4) > I keep getting bugged by this bug for info. Can anyone explain what is > needed? > I don't see how I can change the red options. > Anyone who can, please do so. thanks. You receive updates as the original reporter. If you d not want this you can click "ignore bug mail".
In NetworkManager, you can configure "connectivity" check (as explained in `man NetworkManager.conf`, and which the file 20-connectivity-fedora.conf does) With that, NetworkManager will periodically try to get the configured HTTP page, and determine a per-interface+per-address-family connectivity state. That connectivity state is also combined to a global connectivity state. Those connectivity states are exposed on D-Bus. Btw, also, if a device is detected to have no connectivity, then the route metric of the defalut route is bumped by +20000. $ busctl get-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Connectivity That's about all that NetworkManager does. Then some other GNOME component listens to the connectivity state, and may decide to show a login window (a browser). The bug is reported against NetworkManager. Since all that NetworkManager does is determining the (global) connectivity state, it seems the only problem that it could have, is to determine the wrong state (unless you propose to extend the current connectivity check functionality in a significant way). To find out whether the connectivity state is wrong, one needs to check the logs and reason why a certain state is wrong. For that, enable `level=TRACE` logging. Read DEBUGGING in `man NetworkManager`. Then search for lines like "connectivity". In particular, take note of the times when the state seems wrong, so that it can be found in the (huge) log. Otherwise, maybe the GNOME component should be smarter. E.g. maybe it shows the login window in some cases where it clearly should not. But again, from the description it's not very clear what exactly is wrong or how to reproduce this.
to be clear, the next step to investigate this is by collecting level=TRACE logs of NetworkManager, and check what it says about the connectivity state, at the time when the window pops up. Does it say "portal"? Then the GNOME component would be right to show the window and one would have to investigate why the connectivity state is wrong... Otherwise, if it says "full" connectivity and the window pops up, then the GNOME component needs to be investigated. I don't even know the name of the GNOME component. In the past, it was called portal-helper...