After updating my kernel to 5.8.4/6 (was 4, then updated to 6, but no change) Gnome fails to load successfully, and I get to just a blank screen with flashing underscore. I can change TTY to get to a terminal but to get into Gnome I have to use kernel 5.7.17.
I have tried downgrading Gnome from current 3.36.5 to 3.36.1, the oldest in the repo. I checked/reinstalled the Nvidia driver from RPM fusion and am running 450.57, the second newest currently available.
Below is a collection of what I believe to be relevant logs, I only see these errors when using the newer kernel versions and not when I boot with the 5.7 kernel I have available. Researching the individual errors has led me to some almost relevant resources or sources that do no have a real resolution:
https://bugzilla.redhat.com/show_bug.cgi?id=1796544
Please let me know what other troubleshooting steps I can take. I was not able to find any currently open bugs, besides some semi-relevant bug reports from the testing days last week/two weeks ago that also did not have additional info.
Sep 08 22:50:14 WS-1000-Fedora gnome-session-binary[3062]: Entering running state
Sep 08 22:50:14 WS-1000-Fedora gnome-session[3062]: gnome-session-binary[3062]: GnomeDesktop-WARNING: Could not create transient scope for PID 3249: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3249 does
Sep 08 22:50:14 WS-1000-Fedora gnome-session-binary[3062]: GnomeDesktop-WARNING: Could not create transient scope for PID 3249: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3249 does not exist.
Sep 08 22:50:14 WS-1000-Fedora gnome-session[3062]: gnome-session-binary[3062]: GnomeDesktop-WARNING: Could not create transient scope for PID 3254: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3254 does >
Sep 08 22:50:14 WS-1000-Fedora gnome-session-binary[3062]: GnomeDesktop-WARNING: Could not create transient scope for PID 3254: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3254 does not exist.
Sep 08 22:50:14 WS-1000-Fedora systemd[2502]: gnome-launched-user-dirs-update-gtk.desktop-3368.scope: Failed to add PIDs to scope's control group: No such process
Sep 08 22:50:14 WS-1000-Fedora systemd[2502]: gnome-launched-user-dirs-update-gtk.desktop-3368.scope: Failed with result 'resources'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit UNIT has entered the 'failed' state with result 'resources'.
Sep 08 22:50:14 WS-1000-Fedora systemd[2502]: Failed to start Application launched by gnome-session-binary.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit UNIT has finished with a failure.
--
-- The job identifier is 428 and the job result is failed.
Sep 08 22:50:14 WS-1000-Fedora systemd[2502]: Started Application launched by gnome-session-binary.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 440.
-- Reboot --
Sep 08 22:08:52 WS-1000-Fedora systemd[1]: Starting GNOME Display Manager...
Sep 08 22:08:52 WS-1000-Fedora systemd[1]: Started GNOME Display Manager.
Sep 08 22:09:01 WS-1000-Fedora gdm-password][2778]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=daco
Sep 08 22:09:01 WS-1000-Fedora gdm-password][2778]: gkr-pam: unable to locate daemon control file
Sep 08 22:09:01 WS-1000-Fedora gdm-password][2778]: gkr-pam: stashed password to try later in open session
Sep 08 22:09:07 WS-1000-Fedora gdm-password][2785]: gkr-pam: unable to locate daemon control file
Sep 08 22:09:07 WS-1000-Fedora gdm-password][2785]: gkr-pam: stashed password to try later in open session
Sep 08 22:22:57 WS-1000-Fedora systemd[1]: Stopping GNOME Display Manager...
Sep 08 22:22:57 WS-1000-Fedora gdm[1597]: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
Sep 08 22:22:57 WS-1000-Fedora gdm[1597]: Freeing conversation 'gdm-password' with active job
Sep 08 22:22:57 WS-1000-Fedora gdm[1597]: Tried to look up non-existent conversation gdm-launch-environment
Sep 08 22:22:57 WS-1000-Fedora gdm[1597]: Freeing conversation 'gdm-launch-environment' with active job
Sep 08 22:22:57 WS-1000-Fedora systemd[1]: gdm.service: Succeeded.
Sep 08 22:22:57 WS-1000-Fedora systemd[1]: Stopped GNOME Display Manager.
-- Reboot --
Sep 08 22:23:43 WS-1000-Fedora systemd[1]: Starting GNOME Display Manager...
Sep 08 22:23:43 WS-1000-Fedora systemd[1]: Started GNOME Display Manager.
Sep 08 22:23:43 WS-1000-Fedora gdm[2622]: GdmDisplay: Session never registered, failing
Sep 08 22:23:43 WS-1000-Fedora gdm[2622]: Child process -3047 was already dead.
Sep 08 22:23:43 WS-1000-Fedora gdm[2622]: Child process -3047 was already dead.
Sep 08 22:23:44 WS-1000-Fedora gdm[2622]: Child process -3421 was already dead.
Sep 08 22:38:14 WS-1000-Fedora systemd[1]: Stopping GNOME Display Manager...
Sep 08 22:38:14 WS-1000-Fedora systemd[1]: gdm.service: Succeeded.
Sep 08 22:38:14 WS-1000-Fedora systemd[1]: Stopped GNOME Display Manager.
Sep 08 22:38:36 WS-1000-Fedora systemd[1]: Starting GNOME Display Manager...
Sep 08 22:38:36 WS-1000-Fedora systemd[1]: Started GNOME Display Manager.
Sep 08 22:38:36 WS-1000-Fedora gdm[5675]: GdmDisplay: Session never registered, failing
Sep 08 22:38:36 WS-1000-Fedora gdm[5675]: Child process -5695 was already dead.
Sep 08 22:38:36 WS-1000-Fedora gdm[5675]: Child process -5695 was already dead.
Sep 08 22:38:36 WS-1000-Fedora gdm[5675]: Child process -5732 was already dead.