What is wrong with apparmor?

5.19 is dangerous. It can damage intel laptop display. To avoid.

I have tried this solution: copy old "debian" to EFI as "daedalus" than
efibootmgr --create --disk=/dev/nvme0n1 --part=1 --label="daedalus" --loader='EFI\daedalus\shimx64.efi'

It appears in refind menu and it boots new chimaera!

Before I had windows (on veracrypt), daedalus and space for other linux to test: 1 partition for boot and one for encrypted root. In my very first partition, EFI partition I had many folders: refind, debian (which means devuan). When I installed ubuntu I had ubuntu folder and the same name appeared in refind's menu.
All my devuan installation are made from debian, so the folder name is debian.
So, I've installed one more debian, converted it to chimaera and all of this alongside daedalus.

Now I cannot boot daedalus. All my important staf is in daedalus. Boot partition is ok, luks with daedalus is ok. I also had old folder EFI/debian. I've renamed this folder and put it in /EFI/daedalus. It did not help. I've installed refind again and got the same result.

# efibootmgr -uv
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,DC5B,0000,0002
Boot0000* Windows Boot Manager    HD(1,GPT,b152e14e-61f7-4570-b496-29920c69a074,0x800,0x200000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)䥗䑎坏S
Boot0002* debian    HD(1,GPT,b152e14e-61f7-4570-b496-29920c69a074,0x800,0x200000)/File(\EFI\DEBIAN\SHIMX64.EFI)
Boot0003* rEFInd Boot Manager    HD(1,GPT,b152e14e-61f7-4570-b496-29920c69a074,0x800,0x200000)/File(\EFI\REFIND\REFIND_X64.EFI)
BootDC5B* VeraCrypt BootLoader (DcsBoot)    HD(1,GPT,b152e14e-61f7-4570-b496-29920c69a074,0x800,0x200000)/File(\EFI\VERACRYPT\DCSBOOT.EFI)

Changed boot menu in bios from refind to hard drive - the same

It is strange. The package gnome-keyring has not been updated. Some packages which names starts with gnome- where updated.
I do not understand, gnome creates so much problem!
I have to move from ceres to daedalus. After ~ 2 month on cerres the system was broken completely and irreversibly. System update of cause. Now the story repeats with daedalus. It breaks every 2-3 weeks.

I also reverted to 5.18 kernel, as vmware does not work correctly with 5.19 So slow even with spectre_v2=off or mitigations=off
I have to use vmware as virtualbox neither work correctly nor KVM where virtfs is partly broken too.

Do you really have no issues after updates?

/usr/bin/gnome-keyring-daemon --daemonize --login   100% CPU

pstree gives this

init─┬─ModemManager───2*[{ModemManager}]
     ├─NetworkManager───2*[{NetworkManager}]
     ├─accounts-daemon───2*[{accounts-daemon}]
     ├─at-spi-bus-laun─┬─dbus-daemon
     │                 └─3*[{at-spi-bus-laun}]
     ├─at-spi2-registr───2*[{at-spi2-registr}]
     ├─avahi-daemon───avahi-daemon
     ├─bluetoothd
     ├─cron
     ├─cups-browsed───2*[{cups-browsed}]
     ├─cupsd
     ├─2*[dbus-daemon]
     ├─dbus-launch
     ├─dconf-service───2*[{dconf-service}]
     ├─dnscrypt-proxy───12*[{dnscrypt-proxy}]
     ├─dnsmasq───dnsmasq
     ├─elogind-daemon
     ├─evolution-addre───5*[{evolution-addre}]
     ├─evolution-calen───8*[{evolution-calen}]
     ├─evolution-sourc───3*[{evolution-sourc}]
     ├─gedit───4*[{gedit}]
     ├─6*[getty]
     ├─gjs───10*[{gjs}]
     ├─gnome-keyring-d───3*[{gnome-keyring-d}]

I still need password with doas inspite of:

permit username as root
permit nopass username as root

in /etc/doas.conf

Strange

https://www.ventoy.net/en/index.html
Probably this is the best solution for installation media. One need to create ventoy flash drive only once. Just copy iso file to that drive (or as many iso as possible) and boot from flash drive.