I installed F34 (after a F33->F34 upgrade failure) and set up everything I needed on the first boot. However after re-booting a second time, the boot screen got stuck for about 2 minutes under Starting Switch Root until init sendt a SIGTERM. Under journalctl I see that d-bus fails to start, but it’s not clear why.
When starting under single mode everything “works” fine: After the folowing message
Cannot apen access to console, the root account is locked.
There’s a switch to the default target and then I get the GDM login screeen.
Your journalctl link seems to be broken so it’s hard to tell, but it sounds like you could be encountering this dracut issue which can occur if you have a Bluetooth mouse/keyboard/something connected to your computer. There are some tips on disabling the new dracut Bluetooth support in that issue. Are you able to add the omit_dracutmodules line and run dracut -f successfully in single user mode?