High number of Selinux issues after upgrading to Fedora 36

Not really flooding but a lot of persistent and repeating SELinux errors.
BTW. The kernel option selinux=0 is for me a workaround. As noted in /etc/selinux/config changing to SELINUX=permissive may not be enough.

Thanks for the hint, to narrow the problem by temporary disabling SELinux. Yes this is only a lead and not as solution. Tomorrow I’m going to ask in a new tread, how autorelable can cause something like: Failed at step EXEC spawning /usr/lib/systemd/systemd: Permission denied,

Oh and I can see the Grub menu alright, but all the kernels listed are the 5.12.9-300.fc34 one or older ones

can you do
sudo grubby --info=ALL

Thanks

Have you tried dnf autoremove to see what files may not be needed anymore since you upgraded.

Hi @forgottenmacaroni
Perhaps you trapped into the same ‘reinstall’ issue, like me.
I was able to solve my problem with the doing the official workaround right.

Here’s the output of sudo grubby --info=ALL:

index=0
kernel="/boot/vmlinuz-5.17.11-300.fc36.x86_64"
args="ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.luks.uuid=luks-dc093f83-04a1-45bd-8d69-0386733b29d1 rd.lvm.lv=fedora_localhost-live/swap rhgb quiet snd_hda_intel.dmic_detect=1 loglevel=3 snd_hda_intel.dmic_detect=0"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.17.11-300.fc36.x86_64.img"
title="Fedora Linux (5.17.11-300.fc36.x86_64) 36 (Thirty Six)"
id="b5aecdd710d14ca682224c6ca7250831-5.17.11-300.fc36.x86_64"
index=1
kernel="/boot/vmlinuz-5.17.8-300.fc36.x86_64"
args="ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.luks.uuid=luks-dc093f83-04a1-45bd-8d69-0386733b29d1 rd.lvm.lv=fedora_localhost-live/swap rhgb quiet snd_hda_intel.dmic_detect=1 loglevel=3 snd_hda_intel.dmic_detect=0"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.17.8-300.fc36.x86_64.img"
title="Fedora Linux (5.17.8-300.fc36.x86_64) 36 (Thirty Six)"
id="b5aecdd710d14ca682224c6ca7250831-5.17.8-300.fc36.x86_64"
index=2
kernel="/boot/vmlinuz-0-rescue-b5aecdd710d14ca682224c6ca7250831"
args="ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.luks.uuid=luks-dc093f83-04a1-45bd-8d69-0386733b29d1 rd.lvm.lv=fedora_localhost-live/swap rhgb quiet snd_hda_intel.dmic_detect=1 loglevel=3 snd_hda_intel.dmic_detect=0"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-0-rescue-b5aecdd710d14ca682224c6ca7250831.img"
title="Fedora (0-rescue-b5aecdd710d14ca682224c6ca7250831) 34 (Thirty Four)"
id="b5aecdd710d14ca682224c6ca7250831-0-rescue"
1 Like

I don’t think I have the same issue, my problem comes from my system using a Fedora 34 kernel

I just did, no effect sadly.

I mentionned it before, but could there be a link between the NVIDIA kernel module missing. Falling back to nouveau error I have at boot and the fact that that this old kernel is being used?

grubby --default-kernel

if it’s not one of the F36 ones.
you can try:
grubby --set-default="/boot/vmlinuz-5.17.11-300.fc36.x86_64"

before you reboot

touch /.autorelabel

grubby --default-kernel outputs /boot/vmlinuz-5.17.11-300.fc36.x86_64, I therefore did not ran the following commands as say…

The old kernel is from the rescue image of grub. It would be the original rescue kernel from when you originally installed Fedora Linux onto your system. It doesn’t update when you update or upgrade your system in Workstation.

Hmm ok. But why is my system using it and how can I fix this?..

I note the listing you show indicates your index 2 kernal as …

It isn’t your booted kernel though as you have found by using the command @grumpey mentioned.

sudo cat /boot/efi/EFI/fedora/grub.cfg

sudo ls /boot/efi/EFI

boot_indeterminate=7

Does not seem right based on /etc/grub.d/10_reset_boot_success

Maybe I misunderstand your post but In the grub menu (or at least the menu I can see before my system starts up), the first 3 kernels are fc34 ones and the “rescue” one is fc31, which should be the one I initially installed.

I’m not sure to understand

Here’s the output of sudo cat /boot/efi/EFI/fedora/grub.cfg:

search --no-floppy --fs-uuid --set=dev 88634689-721c-42f6-b814-287fa850a72e
set prefix=($dev)/grub2
export $prefix
configfile $prefix/grub.cfg

Here’s the output of sudo ls /boot/efi/EFI:

BOOT  fedora

boot_indeterminate=7
Does not seem right based on /etc/grub.d/10_reset_boot_success

So you mean I did something wrong or do you just find it strange?

Don’t worry, I’m the one not understanding in this case.