SUMMARY Since last week, every time my notebook connects to a network, be it wired or wireless, Plasma displays a notification about the need to log in to said network. If I click on it, it opens http://networkcheck.kde.org/. This behaviour is maintained even after I changed /usr/lib/NetworkManager/conf.d/30-connectivity-kde.conf to point to http://nmcheck.gnome.org/check_network_status.txt. It is noteworthy that this only happens on my notebook and not on my other devices (two desktops, one tablet). I am out of ideas as to what may be causing this or how to identify the cause, as the behaviour persists across reboots and across all networks I've tried (including hotspots through two different phones using different mobile operators). STEPS TO REPRODUCE 1. Connect to a network OBSERVED RESULT Plasma displays a notification says I have to log in for the network to work. EXPECTED RESULT If there is no actual captive portal, Plasma doesn't display said notification. SOFTWARE/OS VERSIONS Linux: KDE neon KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION
There haven't been any meaningful changes to the plasma-nm code in the 5.24 branch for a month; see https://invent.kde.org/plasma/plasma-nm/-/commits/Plasma/5.24. I suspect this was caused by an update to some other system component. Did networkmanager, networkmanager-qt, or the kernel get updated recently?
(In reply to Nate Graham from comment #1) > There haven't been any meaningful changes to the plasma-nm code in the 5.24 > branch for a month; see > https://invent.kde.org/plasma/plasma-nm/-/commits/Plasma/5.24. > > I suspect this was caused by an update to some other system component. Did > networkmanager, networkmanager-qt, or the kernel get updated recently? It's possible, but I haven't updated any of the components you mentioned recently. To be more precise, I did update the kernel, but this problem started showing up a couple of weeks later. Doing a search on which packages were updated I found libkf5networkmanagerqt6, which was updated from version 5.91.0-0xneon+20.04+focal+release+build32 to 5.92.0-0xneon+20.04+focal+release+build33. I have no idea if this may be related.
Sounds like it could be.
A few weeks ago I started using the wired connection instead of wifi and I believe it's the same problem as reported here, although I don't remember having this issue with wireless. I can share a screenshot if that helps. System info: Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.17.1-3-MANJARO (64-bit) Graphics Platform: X11
I want to add that when I click the Login button in the notification, it opens the browser to http://networkcheck.kde.org/
*** This bug has been marked as a duplicate of bug 451139 ***
(In reply to Nate Graham from comment #6) > > *** This bug has been marked as a duplicate of bug 451139 *** No, these two are not the same at all. In the other bug's case, the issue is that the connection is not activated; in this case, the issue is that Plasma says that I have to go through a captive portal, but there is no such portal and the connection works perfectly well.
This started about a month ago for me too, I am now asked to log in to a fixed network after every boot/wakeup. I read that it is claimed that there were possibly changes in some other component, but I am using Neon. Can I expect the components of this distribution to work seamlessly or do developers only work on the KDE part without testing as a whole? I am asking this since I am considering moving to another distro, that is better maintained and more stable as a whole. Thanks for any insights!
I am also getting this behavior with up-to-date packages on Arch Linux: KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0
Found this issue on my system. Was due to a change I made last year but the issue only showed up a few months ago. I had changed the network connectivity check to gnome (there was a temporary issue with manjaro network check and I forgot to change back), maybe I'm wrong but I assume with an update manjaro defaulted back to their own. So in /etc/NetworkManager/conf.d/20-rc-manager.conf and /usr/lib/NetworkManager/conf.d/20-connectivity.conf, I had in one file: [connectivity] uri=http://nmcheck.gnome.org/check_network_status.txt and the other file had: [connectivity] uri=http://ping.manjaro.org/check_network_status.txt Plasma seemed to get confused and the system showed a notification popup that a login was needed but only took me to the kde nework check link I provided in a previous comment. The tray icon persistently showed network-wired-activated-limited, but clicking on it, the popup for networks showed the correct network-wired-activated icon.
Could it be that NM and/or the Plasma applet respectively does not correctly deal with HTTPS redirects? These seem to happen for both http://networkcheck.kde.org/ and http://nmcheck.gnome.org/check_network_status.txt. Once I change the URLs to https, the check succeeds again.
(In reply to Thilo-Alexander Ginkel from comment #11) > Could it be that NM and/or the Plasma applet respectively does not correctly > deal with HTTPS redirects? These seem to happen for both > http://networkcheck.kde.org/ and > http://nmcheck.gnome.org/check_network_status.txt. > > Once I change the URLs to https, the check succeeds again. I've tried this, with no success. I admit I haven't rebooted the machine yet, so I'll have to test this after a reboot as well to confirm 100%. In any case, I'm marking the bug as "confirmed" since it appears to affect multiple people.
(In reply to Riccardo Robecchi from comment #12) > (In reply to Thilo-Alexander Ginkel from comment #11) > > Could it be that NM and/or the Plasma applet respectively does not correctly > > deal with HTTPS redirects? These seem to happen for both > > http://networkcheck.kde.org/ and > > http://nmcheck.gnome.org/check_network_status.txt. > > > > Once I change the URLs to https, the check succeeds again. > > I've tried this, with no success. I admit I haven't rebooted the machine > yet, so I'll have to test this after a reboot as well to confirm 100%. > In any case, I'm marking the bug as "confirmed" since it appears to affect > multiple people. I can confirm it doesn't work, after a few reboots.
I believe this is caused by the network blocking UDP. Because TCP still works, the web request goes through and doesn't redirect to the network login page. For me a hotel network kept nagging me about needing to login while internet worked fine. It was when wireguard or torrents didn't work when I started to have an idea why it might be happening.
In my case at least, it applies to every single network and I am sure that UDP works on at least some of them, therefore I would exclude this as the cause for the bug I am personally seeing.
I see. I'll create a separate issue later today
At least in my case, the bug appears to now be fixed. Is anyone else still experiencing it?
(In reply to Riccardo Robecchi from comment #17) > At least in my case, the bug appears to now be fixed. Is anyone else still > experiencing it? I have actually started experiencing this issue for the first time today. It's on Ubuntu 22.04 with updates installed within the last month.
(In reply to GGG from comment #18) > I have actually started experiencing this issue for the first time today. > It's on Ubuntu 22.04 with updates installed within the last month. Is this on Ubuntu 22.04 with GNOME?
Created attachment 160461 [details] attachment-3623165-0.html No, it is on KDE. I do not use Gnome packages on that system. Суббота, 22 июля 2023, 22:44 +03:00 от Riccardo Robecchi <bugzilla_noreply@kde.org>: >https://bugs.kde.org/show_bug.cgi?id=452355 > >--- Comment #19 from Riccardo Robecchi < sephiroth_pk@hotmail.it > --- >(In reply to GGG from comment #18) >> I have actually started experiencing this issue for the first time today. >> It's on Ubuntu 22.04 with updates installed within the last month. > >Is this on Ubuntu 22.04 with GNOME? > >-- >You are receiving this mail because: >You are on the CC list for the bug. С наилучшими пожеланиями, Григорий Речистов. Med vänliga hälsningar, Grigory Rechistov With best regards, Grigory Rechistov
Leaving this open then.
Is anyone experiencing it with Plasma 5.27?
Is this still reproducible in Plasma 6.1?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Nate Graham from comment #23) > Is this still reproducible in Plasma 6.1? I never had the problem anymore for at least one year. Suspect some relevant component updated.
I haven't had this issue for a while, either, and I am still on Plasma 5.27. I'm closing this as "worksforme". Thanks for everyone's help.