Gnome failing to load after upgrade to Kernel 5.8.4/6

Ask Fedora Ask in English
, ,
1

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.
2

What version of fedora?
Which gnome package are you looking at.?
What video card and driver are you using?

I am running F32, fully updated and always keep everything updated from the fedora repos and have never had a problem with gnome. My system has kernel 5.8.6 and gnome-desktop 3.36.5 (at present) . My gnome-session is at 3.36.0.

I use only the fedora and updates repos for the system and in over 10 years gnome has never had a problem for me.

Are you mixing repos or installing packages from outside the official fedora repos?
It is known that mixing repos or installing packages from outside can cause problems because sometimes there are tweaks done by the packagers for the distro to prevent users encountering minor problems.
It is also known that updating only one part of the system may break because it could depend on something in another area that did not get a matching update.

I would recommend a full update using only the fedora updates repo and see what happens then. I find it hard to believe a properly updated gnome would cause your problem, but it could easily be something outside gnome, such as the video card and driver, that is killing it.

BTW, I also never use the modular repos. I have had problems with that approach so I keep the fedora modular repos disabled.

2 Likes
3

F32 Desktop
gnome-shell.x86_64, 3.36.5-1.fc32, installed from @updates
I have a GTX1060 and was using the closed-source Nvidia drivers

Thanks for your reply, it made me question the drivers as that was the only component that was not from the official repos. I switched back to Noveau, and then installed the driver directly from RPM Fusion rather than through the Nvidia installer and am no longer having issues.

I think what might have happened is when the new kernel was installed, it removed part of the Noveau blacklisting, and when booting the two drivers were conflicting. I can’t confirm that, never found anything more than what I included in the original logs.

Everything I have installed otherwise that would affect Gnome/kernel, that is not just a standard desktop application is from the standard Fedora/Updates repos, nothing installed from modular.

4

Glad I could help!.
Some time back I also installed directly from nvidia, but when I found the rpmfusion drivers I switched since rpmfusion keeps the drivers up to date and they can be updated from the repo automagically.

It may not have been an alteration in the blacklisting, but simply that the newly installed kernel was not compatible with the driver as it was installed. Kernel modules are often strictly designed for the matching kernel and with an update of the kernel the drivers should be updated as well.
Using the akmod-nvidia package from rpmfusion and the kernel and gcc packages that are required to do module rebuilds helps to keep things in sync and avoid problems with drivers.

Would you please mark your last post as the solution so others can see how your problem was solved.

1 Like
5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.