You need to log in to this network

[Ben]

This morning I had 6 new notifications from Network Management - not at regular intervals, some at 3x minutes, some over an hour apart.

This issue has popped up (sic) for a week or two now… I’m connected via LAN to my fibre router and internet is working well enough.

Following through I get a link to https://networkcheck.kde.org/ which is just a blank page that displays the word ‘OK’.

I don’t think jctl has anything interesting -

jctl (jctl='journalctl -p 3 -xb')

-- Journal begins at Sat 2021-07-24 09:52:59 +07, ends at Fri 2021-07-30 08:41:49 +07. --
Jul 28 15:33:48 Evo systemd-udevd[231]: /usr/lib/udev/rules.d/99-indi_auxiliary.rules:5 Invalid value "/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb >
Jul 28 15:33:48 Evo kernel: snd_hda_codec_hdmi hdaudioC0D0: Monitor plugged-in, Failed to power up codec ret=[-13]
Jul 28 15:33:49 Evo nmbd[623]: [2021/07/28 15:33:49.935207,  0] ../../lib/util/become_daemon.c:147(daemon_status)
Jul 28 15:33:49 Evo nmbd[623]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
Jul 28 15:33:49 Evo nmbd[623]: [2021/07/28 15:33:49.936208,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
Jul 28 15:33:49 Evo nmbd[623]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
Jul 28 15:33:59 Evo nmbd[623]: [2021/07/28 15:33:59.941570,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Jul 28 15:33:59 Evo nmbd[623]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Jul 28 15:34:00 Evo smbd[1147]: [2021/07/28 15:34:00.031641,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
Jul 28 15:34:00 Evo smbd[1147]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Jul 28 15:34:02 Evo kwin_x11[1357]: kwin_xkbcommon: XKB: /home/ben/.XCompose:9:29: unrecognized keysym "UOE3F" on right-hand side
Jul 28 15:34:22 Evo nmbd[623]: [2021/07/28 15:34:22.974993,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Jul 28 15:34:22 Evo nmbd[623]:   *****
Jul 28 15:34:22 Evo nmbd[623]: 
Jul 28 15:34:22 Evo nmbd[623]:   Samba name server EVO is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.104
Jul 28 15:34:22 Evo nmbd[623]: 
Jul 28 15:34:22 Evo nmbd[623]:   *****
Jul 28 15:34:22 Evo nmbd[623]: [2021/07/28 15:34:22.975625,  0] ../../source3/nmbd/nmbd_browsesync.c:355(find_domain_master_name_query_fail)
Jul 28 15:34:22 Evo nmbd[623]:   find_domain_master_name_query_fail:
Jul 28 15:34:22 Evo nmbd[623]:   Unable to find the Domain Master Browser name WORKGROUP<1b> for the workgroup WORKGROUP.
Jul 28 15:34:22 Evo nmbd[623]:   Unable to sync browse lists in this workgroup.
Jul 28 15:34:24 Evo kwin_x11[1973]: kwin_xkbcommon: XKB: /home/ben/.XCompose:9:29: unrecognized keysym "UOE3F" on right-hand side
Jul 28 15:34:28 Evo pulseaudio[1451]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote applica>
Jul 28 15:34:31 Evo kwin_x11[1998]: kwin_xkbcommon: XKB: /home/ben/.XCompose:9:29: unrecognized keysym "UOE3F" on right-hand side
Jul 28 15:49:30 Evo nmbd[623]: [2021/07/28 15:49:30.722333,  0] ../../source3/nmbd/nmbd_browsesync.c:355(find_domain_master_name_query_fail)
Jul 28 15:49:30 Evo nmbd[623]:   find_domain_master_name_query_fail:

I just created a file /etc/NetworkManager/conf.d/20-connectivity.conf and pasted [connectivity] .set.enabled=false

Not sure if this is a good plan.

[Pcwolf]

I am also receiving those notifications. In addition, the wifi icon in the dock is showing an orange ! indicating degraded internet connectivity, although speeds and internet are working normally.

[westyvw]

I have these issues as well:

KDE saying I need to log in , and the Orange notification saying I have limited connectivity.

[Ben]

So this more likely is a problem with the check than with my internet connection, that’s good to know.
So is this an archy problem? I see few decent results from the web - nice to see it’s more common than I imagined.

[westyvw]

So the question is, did this latest update cause this issue? I didnt have it before, but I havent seen any other posts except here.

[Tempus]

Same here! Just started at some random point Thurs. night. BEFORE I accepted the update, just random in the middle of surfing various sites. Very annoying!
In case it matters I’m running Manjaro kde.
Just searching for a answer, or a cause.
Geez, there it goes again. I will have to try and time it if I have a chance.

[westyvw]

Maybe its the attempt to ping a server that is down, as in this thread here?

KDE Network Manager and "limited connectivity"

That was the right path, I created /etc/NetworkManager/conf.d/20-connectivity.conf as per the wiki but it didn’t tell you how to disable the check, I tried their sample and commenting out that line thinking it being there but commented out would do it, but some further googling let me to adding which did it! It’s been hours and it hasn’t come back, prior it took about 30min or so and would do it every time.

[Falav]

Manjaro website down =>

Manjaro.org is down

Is it possible that http://ping.manjaro.org/check_network_status.txt is down? Because that’s what /usr/lib/NetworkManager/conf.d/20-connectivity.conf is checking.

[Downtime] manjaro.org; ping.manjaro.org

As mentioned yesterday on Twitter already, we have some issues with manjaro.org and ping.manjaro.org. This might continue to be the case for today. [image] Old IPs 2a01:4f8:150:448b::1 176.9.38.148 New IPs 2a01:4f8:c0c:51f3::1 116.203.91.91 We updated our DNS entries to point to the new server. However this may take time to been picked up by all of them. You can add the following entries to your /etc/hosts file and restart dnsmasq: sudo systemctl restart dnsmasq.service 116.203.91.91 ma…

[blackSP]

I have the same issue I think but the randomly appearing message is that I need to log in to my VPN. However, like always my VPN is up and running and masking my IP address. Issue started also after accepting the latest update.

[realmain]

I have a wired connection and have also been having this issue ever since the last update as well.

[fhins]

It is fixed now (wired and wireless)!