[Stable Update] 2022-05-23 - Kernels, Toolchain, NVIDIA, Mesa, KDE, Qt, Maui, LibreOffice, Plasma, Firefox, Thunderbird

[Daniel-I]

I think this is related to… "Hotspot Login" pops up in Network Login app when waking from sleep - #17 by GaVenga
I use ethernet, not wifi, and I am getting “Wired Ethernet: Connected to Ethernet (log in required)” on mouseover of my network connection systray icon… there was a similar “Network Manager” popup I closed; dismissing it knowing I didn’t need to login to my ethernet network before realizing it was also echo’d in the systray.

In my case, /usr/lib/NetworkManager/conf.d/20-connectivity.conf is pointing to http://ping.manjaro.org/check_network_status.txt, which if I open in a browser throws a 404 Page not found.

EDIT:
I’ve updated my file to include a few of the typical replacements/options, opting to use KDE for now:

[connectivity]
#uri=http://ping.manjaro.org/check_network_status.txt
#uri=http://www.archlinux.org/check_network_status.txt
#uri=http://nmcheck.gnome.org/check_network_status.txt
uri=http://networkcheck.kde.org

…and all was well after a service restart with $ sudo systemctl restart NetworkManager

[GaVenga]

temporary Work-Arround:

Warning pops up and says that i have a login required?

alternativ change the line in /usr/lib/NetworkManager/conf.d/20-connectivity.conf like this: connectivity] [uri=http://ping.manjaro.org/check_network_status.txt] uri=http://nmcheck.gnome.org/check_network_status.txt and: sudo systemctl restart NetworkManager

[n_b]

I’m not sure about the errors with
journalctl -r
but the UI errors seemed to have been fixed after a few restarts.

[asormanni]

Hello,
after update, no sound output from any application.

Sound Blaster Z, pipewire-git & wireplumber. Only dummy output sink available.

My solution: rebuild all AUR pipewire packages in use:

pipewire-full-alsa-git
pipewire-full-ffmpeg-git
pipewire-full-git
pipewire-full-jack-client-git
pipewire-full-pulse-git
pipewire-full-v4l2-git
pipewire-full-zeroconf-git

After GNOME session restart, sound worked normally.

Regards.

[goma-chan]

@kebloom

I was unable to activate bluetooth after the update. Bluetoothctl reported no default controller.

My Solution:
Rolling back the kernel solved the issue. I switched from linux517 to linux515.

Same here.
Also Wi-Fi started displaying “log-in required” popup for some reason (it works fine, though).

[winnie]

@goma-chan

Also Wi-Fi started displaying “log-in required” popup for some reason (it works fine, though).

What is "You need to log in to this network" when activating a wired connection?

It seems the site used for the network connection check (http://ping.manjaro.org/check_network_status.txt) is currently down and therefore we get this notification. You can find the address in “20-connectivity.conf” located in /usr/lib/NetworkManager/conf.d I think the problem will disappear once the site is back up.

[goma-chan]

@winnie

What is "You need to log in to this network" when activating a wired connection? - #2 by Xindl

Thank you!

[winnie]

Posts #5 and #6 (in the linked thread) show you a workaround by creating a new .conf file and restarting the NetworkManager service. You can keep this change as a permanent solution too, there’s no harm done.

[goma-chan]

I’ve just noticed that my whole desktop (KDE) went black - no wallpapers, no icons. Any help is appreciated.

[GaVenga]

@winnie

here’s no harm done.

Correct - but: /usr/lib/NetworkManager/conf.d/20-connectivity.conf
exists in system already (I use Gnome)

[brahma]

what is your DE?
with no desktop you mean completely blank screen?
provide more info

[winnie]

Since you’re on KDE.

Are you using dual monitors? Can you test it out with only a single display?

Otherwise, you can try the following to see if it helps out:

1. Log out of KDE

2. Switch to TTY2:

• CTRL + ALT + F2

3. Login to this TTY2 terminal

4. Stop the display-manager service:

• sudo systemctl stop display-manager

5. Move/delete the old kscreen config:

• mv -v $HOME/.local/share/kscreen $HOME/.local/share/kscreen.bak

6. Rebuild the KDE cache:

• kbuildsycoca5 --noincremental

7. Wait about 30 seconds

8. Then finally restart the display-manager service and login to KDE:

• sudo systemctl restart display-manager && exit

[goma-chan]

KDE. Yes completely black screen, but taskbar and windows are OK (that’s why I haven’t even noticed that at first).

[winnie]

@GaVenga

Correct - but: /usr/lib/NetworkManager/conf.d/20-connectivity.conf
exists in system already (I use Gnome)

You’re not supposed to touch that file. You’re supposed to create a new “drop in” file under /etc/NetworkManager/conf.d/

[GaVenga]

Then let us do …/30–stupid.conf
The offending url is inside this holy file - so you ignore “not to touch the earth” file

or nothing will change - although time changes everything
B.t.w.: today is the first day of the rest of your life!

[goma-chan]

@winnie

1. Log out of KDE

2. Switch to TTY2:

• CTRL + ALT + F2

3. Login to this TTY2 terminal

4. Stop the display-manager service:

• sudo systemctl stop display-manager

5. Move/delete the old kscreen config:

• mv -v $HOME/.local/share/kscreen $HOME/.local/share/kscreen.bak

6. Rebuild the KDE cache:

• kbuildsycoca5 --noincremental

7. Wait about 30 seconds

8. Then finally restart the display-manager service and login to KDE:

• sudo systemctl restart display-manager && exit

Thank you, thank you, it did the trick. At first it looked weird with random wallpapers and the taskbar gone, but after resetting the display settings (laptop + external display) it was back to normal.

[GaVenga]

@winnie

a new “drop in” file unde

Doesnot work, because NetworkManager does not care about…

[winnie]

@goma-chan

At first it looked weird with random wallpapers and the taskbar gone, but after resetting the display settings …

That’s because we forced KDE to reset the display settings by renaming/removing the kscreen config folder.

[winnie]

@GaVenga

Doesnot work, because NetworkManager does not care about…

How / what file did you create? Where? What are the contents of this new file? Did you restart the NetworkManager service using systemctl?

[GaVenga]

@winnie

How / what file did you create? Where? What

First I tried: sudo nano /etc/networkManager/conf.d/20-connectivity.conf
(This File did not exist before) with this contents:

[connectivity]
uri=http://nmcheck.gnome.org/check_network_status.txt

Followed by sudo systemctl restart NetworkManager
and -nothing happend/changed.
Then, as I have Internet, an Ubuntu-Forum told me I did wrong.
had to do: sudo nano /usr/lib/NetworkManager/conf.d/20-connectivity.conf
This file already existed, contents:

[connectivity]
uri=http://ping.manjaro.org/check_network_status.txt

Changed to:

[connectivity]
[uri=http://ping.manjaro.org/check_network_status.txt]
uri=http://nmcheck.gnome.org/check_network_status.txt

saved, did sudo systemctl restart Networkmanager
and mission accomplished…