New boot startup weirdness

starting 2-3 weeks ago (i normally update fedora weekly), i have a new behavior on bootup.

the system asks what image i want, and i normally go with the latest.
a few seconds later, my screens go to a mid grey texture and i have an active cursor, which i can move around. but i can’t do anything (that is no reponse to keyboard or mouse clicks).

after 5 minutes (almost exactly), the screens go black, and then i get the normal login window.

this smells like a 5 minute timeout in something (like maybe systemd?).

any clues on what i should look for?[ 13.836644] usbcore: registered new interface driver snd-usb-audio
[ 16.681846] igc 0000:04:00.0 enp4s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 18.742179] rfkill: input handler disabled
[ 19.613195] Bluetooth: RFCOMM TTY layer initialized
[ 19.613204] Bluetooth: RFCOMM socket layer initialized
[ 19.613208] Bluetooth: RFCOMM ver 1.11
[ 442.807478] systemd-journald[824]: /var/log/journal/acb4ab16a7ad414595a26430b200efd7/user-1000.journal: Journal file uses a different sequence number ID, rotating.
[ 443.071250] rfkill: input handler enabled
[ 444.695749] rfkill: input handler disabled

are there other logs i might look at?

the last few lines of dmesg are:

You can use sudo systemd-analyze critical-chain to see where there are delays in booting the system.
Also have a look in the journal for the last boot and see if there are interesting logs sudo journalcrl -b 0

such useful information! here are the lines from journalctl -b 0; we see the 6 min or so gap there.
Feb 10 07:37:41 aardwolf geoclue[2334]: Service not used for 60 seconds. Shutting down…
Feb 10 07:37:41 aardwolf systemd[1]: geoclue.service: Deactivated successfully.
Feb 10 07:37:41 aardwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system>
Feb 10 07:37:41 aardwolf systemd[1]: pcscd.service: Deactivated successfully.
Feb 10 07:37:41 aardwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system>
Feb 10 07:37:42 aardwolf realmd[2452]: quitting realmd service after timeout
Feb 10 07:37:42 aardwolf realmd[2452]: stopping service
Feb 10 07:37:42 aardwolf systemd[1]: realmd.service: Deactivated successfully.
Feb 10 07:37:42 aardwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system>
Feb 10 07:38:39 aardwolf systemd[1]: virtqemud.service: Deactivated successfully.
Feb 10 07:38:39 aardwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system>
Feb 10 07:38:54 aardwolf chronyd[1629]: Selected source 15.204.198.96 (2.fedora.pool.ntp.org)
Feb 10 07:41:46 aardwolf PackageKit[2021]: daemon quit
Feb 10 07:41:46 aardwolf audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system>
Feb 10 07:41:46 aardwolf systemd[1]: packagekit.service: Deactivated successfully.
Feb 10 07:42:35 aardwolf systemd[1861]: Created slice background.slice - User Background Tasks Slice.
Feb 10 07:42:35 aardwolf systemd[1861]: Starting systemd-tmpfiles-clean.service - Cleanup of User’s Temporary F>
Feb 10 07:42:35 aardwolf systemd[1861]: Finished systemd-tmpfiles-clean.service - Cleanup of User’s Temporary F>
Feb 10 07:43:14 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:14 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:14 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:14 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:24 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:24 aardwolf gsd-media-keys[2073]: gvc_mixer_card_get_index: assertion ‘GVC_IS_MIXER_CARD (card)’ f>
Feb 10 07:43:24 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:24 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:24 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:24 aardwolf gnome-shell[1906]: Failed to connect to colord device xrandr-Ancor Communications Inc->
Feb 10 07:43:25 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:25 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:25 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:25 aardwolf gsd-media-keys[2073]: gvc_mixer_card_get_index: assertion ‘GVC_IS_MIXER_CARD (card)’ f>
Feb 10 07:43:25 aardwolf rtkit-daemon[1445]: Successfully made thread 1924 of process 1906 (/usr/bin/gnome-shel>
Feb 10 07:43:25 aardwolf gnome-shell[1906]: Failed to connect to colord device xrandr-Ancor Communications Inc->
Feb 10 07:43:26 aardwolf NetworkManager[1685]: [1707579806.0410] device (wlp5s0): set-hw-addr: set MAC >
Feb 10 07:43:26 aardwolf NetworkManager[1685]: [1707579806.0581] device (wlp5s0): supplicant interface >
Feb 10 07:43:26 aardwolf NetworkManager[1685]: [1707579806.0581] device (p2p-dev-wlp5s0): supplicant ma>
Feb 10 07:43:41 aardwolf audit: BPF prog-id=82 op=LOAD
Feb 10 07:43:41 aardwolf systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon…
Feb 10 07:43:41 aardwolf systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Feb 10 07:43:41 aardwolf audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:syste>
Feb 10 07:43:45 aardwolf gdm-password][2675]: gkr-pam: unable to locate daemon control file
Feb 10 07:43:45 aardwolf audit[2675]: USER_AUTH pid=2675 uid=0 auid=4294967295 ses=4294967295 subj=system_u:sys>

the real question is, what was it doing during 7:37 thru 7:43?

What is the output of sudo systemd-analyze critical-chain?

The time when unit became active or started is printed after the “*” character.
The time the unit took to start is printed after the “+” character.

graphical.target *9.928s
└─multi-user.target *9.928s
└─plymouth-quit-wait.service *7.211s +2.703s
└─systemd-user-sessions.service *7.185s +22ms
└─remote-fs.target *7.176s
└─remote-fs-pre.target *3.899s
└─nfs-client.target *3.899s
└─gssproxy.service *3.892s +6ms
└─network.target *3.890s
└─wpa_supplicant.service *3.886s +3ms
└─basic.target *3.121s
└─dbus-broker.service *3.102s +17ms
└─dbus.socket *3.088s
└─sysinit.target *3.086s
└─systemd-resolved.service *3.027s +59ms
└─systemd-tmpfiles-setup.service *2.925s +76ms
└─import-state.service *.836s +62ms
└─local-fs.target *2.822s
└─backup.mount 2.783s +38ms
└─systemd-fsck
dev-disk-by\x2dlabel-backup.service 1.413s +817ms
└─dev-disk-by\x2dlabel-backup.device
584542y 2w 2d 20h 1min 43.930s +6.991s

(sorry: i translated ‘@’ into ‘*’ because of quoting rules.)

The change would not be necessary if you were to post the content as preformatted text using the </> button on the toolbar (or use triple backquotes [ ``` ] on the lines preceding and following the text you past into the post.

It also would retain the same layout structure as seen on your screen if posted that way.