我的 Kubuntu 22.04 即使在恢复模式下也卡在启动过程中。我怀疑这与最近的更新有关，因为在安装并关闭后，系统再也没有进入登录屏幕。最近安装的软件包列表：
2023-02-02 22:34:44 install bat:amd64 <none> 0.19.0-1ubuntu0.1
2023-02-04 10:38:33 install libllvm15:amd64 <none> 1:15.0.6-3~ubuntu0.22.04.2
2023-02-09 20:22:46 install linux-modules-5.15.0-60-generic:amd64 <none> 5.15.0-60.66
2023-02-09 20:22:49 install linux-image-5.15.0-60-generic:amd64 <none> 5.15.0-60.66
2023-02-09 20:22:50 install linux-modules-extra-5.15.0-60-generic:amd64 <none> 5.15.0-60.66
2023-02-09 20:22:58 install linux-headers-5.15.0-60:all <none> 5.15.0-60.66
2023-02-09 20:23:04 install linux-headers-5.15.0-60-generic:amd64 <none> 5.15.0-60.66
最后是 Kubuntu 的 Discover 要求安装的常规更新。
启动过程在此阶段停止：
[ OK ] Reached target Host and Network Name Lookups
我并不介意重新安装操作系统，但还有其他方法可以修复它吗？此外，可能发生了什么？
感谢您的时间。
以下是 的内容boot.log：
FAILED Failed to start Rotate log files.
See 'systemctl status logrotate.service' for details.
OK Started Self Monitoring and Reporting Technology (SMART) Daemon.
------------ Sat Feb 11 07:54:05 CET 2023 ------------
/dev/sda2: clean, 579416/4890624 files, 7994678/19531264 blocks
FAILED Failed to start Set the console keyboard layout.
FAILED Failed to start Set the console keyboard layout.
FAILED Failed to start Set console font and keymap.
FAILED Failed to start QEMU KVM preparation - module, ksm, hugepages.
FAILED Failed to start Load AppArmor profiles.
See 'systemctl status apparmor.service' for details.
Starting Load AppArmor profiles managed internally by snapd...
Mounting Arbitrary Executable File Formats File System...
编辑：
我使用以前的内核启动，但仍然没有成功。
systemctl status logrotate.service的输出：
○ logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static)
Active: inactive (dead)
TriggeredBy: ● logrotate.timer
Docs: man:logrotate(8)
man:logrotate.conf(5)
systemctl status apparmor.service 的输出：
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-02-12 10:44:19 CET; 12min ago
Docs: man:apparmor(7)
https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 522 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, status=203/EXEC)
Main PID: 522 (code=exited, status=203/EXEC)
CPU: 600us
Feb 12 10:44:19 dave-desktop systemd[1]: Starting Load AppArmor profiles...
Feb 12 10:44:19 dave-desktop systemd[1]: apparmor.service: Main process exited, code=exited, status=203/EXEC
Feb 12 10:44:19 dave-desktop systemd[1]: apparmor.service: Failed with result 'exit-code'.
Feb 12 10:44:19 dave-desktop systemd[1]: Failed to start Load AppArmor profiles.
systemctl status grub-common.service 的输出：
× grub-common.service - Record successful boot for GRUB
Loaded: loaded (/lib/systemd/system/grub-common.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-02-12 11:33:35 CET; 2min 53s ago
Process: 579 ExecStartPre=/bin/sh -c [ -s /boot/grub/grubenv ] || rm -f /boot/grub/grubenv; mkdir -p /boot/grub (code=exited, status=203/EXEC)
CPU: 1ms
Feb 12 11:33:34 dave-desktop systemd[1]: Starting Record successful boot for GRUB...
Feb 12 11:33:35 dave-desktop systemd[1]: grub-common.service: Control process exited, code=exited, status=203/EXEC
Feb 12 11:33:35 dave-desktop systemd[1]: grub-common.service: Failed with result 'exit-code'.
Feb 12 11:33:35 dave-desktop systemd[1]: Failed to start Record successful boot for GRUB.