We we’re able to isolate the restart and shutdown issue. In Arch (June 1st ISO), the splash screen message on Kernel 5.19.3 (restart only) was about network and mirrors list refresh. We are not using Ethernet, turn it OFF in the BIOS removes the bug.
All is good now.
pacman -Qii linux60
Name : linux60
Version : 6.0.0rc2-1
Description : The Linux60 kernel and modules
Architecture : x86_64
URL : https://www.kernel.org/
Licenses : GPL2
Groups : None
@pheiduck is referring to the recent Arch update of grub:
Upgrading grub (2:2.06.r322.gd9b4638c5-1 -> 2:2.06.r322.gd9b4638c5-3)...
:: To use the new features provided in this GRUB update, it is recommended
to install it to the MBR or UEFI. Due to potential configuration
incompatibilities, it is advised to run both, installation and generation
of configuration:
$ grub-install ...
$ grub-mkconfig -o /boot/grub/grub.cfg
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Package (6) Old Version New Version Net Change Download Size
extra/bluez 5.65-2 5.65-3 0.00 MiB
extra/bluez-libs 5.65-2 5.65-3 0.00 MiB
...
done
:: Processing package changes...
(1/6) upgrading bluez [############################################################################] 100%
warning: directory permissions differ on /etc/bluetooth/
filesystem: 755 package: 555
(2/6) upgrading bluez-libs [############################################################################] 100%
(3/6) upgrading gnupg [############################################################################] 100%
...
I got permission warning.
How do I recognize in that case and in general case:
does a package came with erroneously changed permission (bug)
OR
it was updated to proper/more suitable version of permissions
?
OK, I think that my question above can’t have an answer when changes comes from package author: any changes in source code / building processes are a new feature/fix and could not be classified as bug or proper fix at the point of installation to a user machine, cause we have no new usage experience with that new version.
So I guess in general the usual user behavior should be to change permissions according to warnings of mentioned ones.