A. I upraged to fedora 33 from 32 via dnf… After rebooting the upgrade it loads all services then gets stuck for 2hours. then it loads the GDM.
B. I decided why not start afresh… Installed fresh copy of rawhide. Worked fine first 2-3 boots…
I wast trying to figure out what is causing the delay in boot time so I was installling packages and rebooting. On an instance I installed gtk4 then it took 2 hours to reach GDM login screen. I did a fresh install and tried installing chromium also when I reboots it takes long
The only propblem being reported by the bootolog is
[FAILED] Failed to start Virtual Machine and Container Registration Service.
See 'systemctl status systemd-machined.service' for details.
systemctl status systemd-machined.service
● systemd-machined.service - Virtual Machine and Container Registration Service
Loaded: loaded (/usr/lib/systemd/system/systemd-machined.service; static)
Active: failed (Result: exit-code) since Tue 2020-08-04 13:39:15 CAT; 2h 38min ago
Process: 668 ExecStart=/usr/lib/systemd/systemd-machined (code=exited, status=1/FAILURE)
Main PID: 668 (code=exited, status=1/FAILURE)
Aug 04 13:39:14 fedora systemd: Starting Virtual Machine and Container Registration Service...
Aug 04 13:39:14 fedora systemd-machined: Failed to bind to varlink socket: Permission denied
Aug 04 13:39:14 fedora systemd-machined: Failed to fully start up daemon: Permission denied
Aug 04 13:39:15 fedora systemd: systemd-machined.service: Main process exited, code=exited, status=1/FAILURE
Aug 04 13:39:15 fedora systemd: systemd-machined.service: Failed with result 'exit-code'.
Aug 04 13:39:15 fedora systemd: Failed to start Virtual Machine and Container Registration Service.
@bretjoseph I did not update Fedora 33 today, so I can not confirm the kernel is still showing that bug. Did you upgrade to the new nightly Rawhide? And did you see that bug? Now you filed a bug report that bug will end soon.
the booting problem is over but the kernel still doesn’t login whether graphical target greeter nor multi-user target, kernel says something about it cant start sh. I can only log in when I disable selinux=0 on grub. When I try loging in, it brings the login prompt again