Got the `Changing NetworkManager Connectivity-Ping to manjaro.org` notification, but afterwards the app actually connects to ping.manjaro.org (was caught by firewall)
I found odd that by updating
To upgrade (3):
networkmanager 1.32.12-2 (1.32.12-1) extra 3.5 MB
...
Reloading system bus configuration... [6/7]
Changing NetworkManager Connectivity-Ping to manjaro.org [7/7]
Transaction successfully finished.
and after manual turn off and on the network connection I found that the network manager still connects to ping.manjaro.org:80
If I found exact config file, then it’s content is:
i’ve also seen the above packages residing in both “community” and “multilib” repos. mine are from community repo, the ones in multilib repo are updated to the latest.
Summary
$ pacman -Si lib32-libva-mesa-driver
Repository : community
Name : lib32-libva-mesa-driver
Version : 21.3.1-0.1
Description : VA-API implementation for gallium (32-bit)
Architecture : x86_64
URL : https://www.mesa3d.org/
Licenses : custom
Groups : None
Provides : None
Depends On : lib32-libdrm lib32-libx11 lib32-llvm-libs lib32-expat lib32-libelf lib32-libxshmfence lib32-zstd
Optional Deps : None
Conflicts With : None
Replaces : None
Download Size : 3.95 MiB
Installed Size : 11.87 MiB
Packager : Philip Mueller philm@manjaro.org
Build Date : Monday 06 December 2021 03:33:18 PM
Validated By : MD5 Sum SHA-256 Sum Signature
Repository : multilib
Name : lib32-libva-mesa-driver
Version : 21.3.1-1
Description : VA-API implementation for gallium (32-bit)
Architecture : x86_64
URL : https://www.mesa3d.org/
Licenses : custom
Groups : None
Provides : None
Depends On : lib32-libdrm lib32-libx11 lib32-llvm-libs lib32-expat lib32-libelf lib32-libxshmfence lib32-zstd
Optional Deps : None
Conflicts With : None
Replaces : None
Download Size : 3.21 MiB
Installed Size : 11.81 MiB
Packager : Laurent Carlier lordheavym@gmail.com
Build Date : Monday 06 December 2021 02:37:24 PM
Validated By : MD5 Sum SHA-256 Sum Signature
What’s up with 5.15 kernel gen? Why so frequent updates?
Usually 1 update per week, now 3 updates per 3 days already, so another 2 are… urgent? What happen?
Constant need for PC reboots…
If they are urgent, then why 5.15.7 in stable and 5.15.8 in testing still? (Manjaro - Branch Compare)
and we are in unstable branch afterall, sooner we have nothing to alarm functionally, the other branches can get them as well (the last changelog is lenghthy)
@Yochanan Has libreswan been removed? I went to install networkmanager-l2tp which has libreswan as a recommended dependency, but such package is missing in the repo.
libreswan has always been in the AUR and so was networkmanager-l2tp until last February. I’ll let the Arch package maintainer know he forgot to import libreswan along with it.
EDIT: The maintainer decided to drop libreswan from optional dependencies instead of importing it.
~/Desktop ❯ cat /etc/default/grub
(...)
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
(...)
I have btrfs encrypted setup.
GRUB version in boot menu does not match grub package version
Compare
with the
~/Desktop ❯ pamac info grub | grep "Ver"
Version : 2.06-2
Going back to the issue above, it appears to happen only with kernel series 5.15 every time my system boots up from a restart. If I previously power off my system and then I boot it up again with kernel 5.15, then I will be able to manage Bluetooth devices from Gnome Settings. This odd behaviour was introduced for me after this major update, although it never happens with kernel series 5.10.
No big deal, but still I think it’s worth reporting this in case someone else experiences the same in future releases for the other branches.
Updated inxi output below (truncated) for further reference
The `error: sparse file not allowed` issue was fixed
Changed the line to
# GRUB_SAVEDEFAULT=true
ran
sudo update-grub
and rebooted PC: the message was not shown.
So I unveiled the issue while merging .pacnew and in the same time “improving” my “/etc/default/grub” settings.
Thank you, Frede!
The report of version mismatch in the GRUB menu vs grub package remains.
Yeah I had a suspicious soft lockup of Dolphin when I was copying a big file to a NFS network location two days ago, kinda similar issue too. The floating notification froze but copying was actually performed without failure. Copying the same file from network location to USB drive didn’t cause any freezes at all.
I also haven’t found any meaningful info in logs…