Comments
gtwilliams
Log is filling with:
Can't boot when installed on Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz. Boots OK on Intel(R) Xeon(R) W-2225 CPU @ 4.10GHz.
kaddressbook updates now and the Google Contacts are now added as an address book.
@marcdeop you merged it in a copr: gear for f37. It fixed a bug, but it doesn't appear that it's included in this update.
https://download.copr.fedorainfracloud.org/results/marcdeop/gear/fedora-$releasever-$basearch/
Works for me. (The Google Contacts patch isn't here, correct?)
My panel settings were changed -- the height was reset to default. Also 24 hour display on digital clock lost leading zeros for morning times (no big deal, but an unwanted change).
Thank you @jforbes. Sorry for the noise.
Ha!
Found the problem. My system is btrfs with two subvolumes, /root and /home, and /sysroot is mounted with / instead of -o subvol=root. At failure time, I unmounted /sysroot and remounted it properly with -o subvol=root and now the boot sequence resumed without further error. I guess this may be a problem with the initrd? Anyway all kernels after 5.19.2 fail to boot with this bug.
wfm
This and every kernel after 5.19.2-300 fail to boot on my system with "Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing."
How can I debug this problem?
[ 5.107016] gtw systemd[1]: Reached target initrd-switch-root.target - Switch Root. [ 5.108528] gtw systemd[1]: Starting initrd-switch-root.service - Switch Root... [ 5.120164] gtw systemctl[601]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 5.121629] gtw systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE [ 5.121902] gtw systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. [ 5.131371] gtw systemd[1]: Failed to start initrd-switch-root.service - Switch Root.
This and also kernel-5.19.3 fail in initrd-switch-root.service owing to "Specified switch root path /sysroot' does not seem to be an OS tree. os-release file is missing." The /etc/os-release symlink points to /usr/lib/os-release, which exists and looks to be the correct data. My work-around has been to fall back to kernel-5.19.2, which boots without any problems.
tests pass
I don't know what plugin is causing the AVCs, but I see the same ones that Kamil reported. I never saw the AVCs reported before the F36 update, so I would agree there is a regression.
I get this when installing:
Error: Transaction test error: file /usr/share/config.kcfg/specialmailcollections.kcfg from install of kf5-akonadi-mime-22.04.1-1.fc36.x86_64 conflicts with file from package kdepimlibs-4.14.10-39.fc36.x86_64
SELinux is preventing systemctl from read access on the file labeled init_t. at boot time after upgrade. Journal has dozens of AVCs on systemctl. type=AVC msg=audit(1653078042.660:584): avc: denied { read } for pid=2859 comm="systemctl" scontext=system_u:system_r:NetworkManager_dispatcher_custom_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=file permissive=1
I deleted my selinux semodule and installed this update and restarted fail2ban. No more AVCs. This updates fixes bz 2083923.
All looks good. Thanks!
This update eliminated the selinux bug. Thank you.
Oops. I mangled the "easy" karma command. See my comments here: https://bugzilla.redhat.com/show_bug.cgi?id=2276314