Unable to log in after upgrading packages

Ask Fedora
,
1

Hello. I am using Fedora 43 Workstation with Kernel 6.19.12-200.fc43.x86_64. So a few days ago I upgraded packages through Software, and since then I have not been able to log in. When I hit Enter after typing in my password, I get sent back to the log in screen. If I try to log in again it gets stuck. I am able to log in to my user from ppy2 after hitting Ctrl + Alt + F2 on the log in screen.

I had a very similar issue after I upgraded to Fedora 43. I found the solution online to remove Wine packages which fixed the issue. But that fix it this time.

I read somewhere that I should run journalctl and check what it says. I’m not really sure what to look for but here are some of the lines that were in red:

systemd-coredump[6434]: Process 6286 (gnome-session-i) of user 1000 dumped core.

gnome-session-i[6286]: Failed to start unit gnome-session-wayland@gnome.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name “org.freedesktop.systemd1” does not exist

dbus-broker-launch[6250]: Ignoring duplicate name ‘org.freedesktop.FileManager1’ in service file ‘/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service’

kernel: rfkill: input handler enabled

gdm-password][5978]: gkr-pam: unable to locate daemon control file

Please let me know if I need to provide anything else.

2

reinstall or downgrade gdm

sudo dnf downgrade gdm

sudo dnf reinstall gdm

3

Doesn’t seem to help.

4

What was the last upgrade:
sudo dnf4 history info last
if that’s not the last upgrade you may need to look through the below to see which transaction was the id.
sudo dnf4 history list
and then
sudo dnf4 history info transaction id

note this is dnf4 because of that’s what’s currently being utilized by gnome-software.

Does :
journalctl --user -b -u gnome-session-\*
Provide anything useful?

What kind of GPU is in this machine?
lspci | awk '/VGA/{print $1}' | xargs -n1 lspci -k -s

And maybe also check:
glxinfo | grep -iE "direct rendering:|OpenGl render"

You may need to install glx-utils for that .. sudo dnf install glx-utils

5

Thanks for the reply!

sudo dnf4 history info last returns this

journalctl --user -b -u gnome-session-\* returns:
-- No entries --

The GPU is a Radeon RX Vega 56.

glxinfo | grep -iE "direct rendering:|OpenGl render" returns:
Error: unable to open display

6

Does it work if you boot off of an older kernel?
Should be able to hold down shift or esc during boot to access the grub menu and select one of the older ones.

thanks

7

I tried Kernel 6.9.11 and 6.9.10 and it doesn’t work.

8

I cant see anything in you dnf history list that should have this effect.

Do you have multiple Desktops installed - Plasma as well as Gnome? Does another desktop boot?

You could try removing Gnome and the reinsalling it, but I dont know what conflicts this will have with your existing software, so proceed with that idea with caution.

You could also update to F44 from TTY2 if you feel comfortable with that.

9

I’ve seen similar problems when an update to nouveau broke support for my (old) Nvidia GPU. Are you using AMD’s ROCm? Does your system have an iGPU?

10

What about looking at the journal after you enter your password and it returns you to gdm?

journalctl -b

Hopefully it’ll have errors there.

Are you using any gnome-extensions? They’re usually one bit that fail for various reasons and are tricky to track down. If you are, it may be worth disabling them all to see if that helps. You can do this using the gnome-extensions command line if you can to a virtual terminal.

@grumpey : just curious—why are we using dnf4 and not just dnf (dnf5)?

11

Because Gnome Software still uses dnf4

12

Ah, right. Haven’t used gnome-software for upgrades in ages.. :grin:

13

You could also try adding a new user from the terminal ..
sudo adduser -m username
sudo passwd username

And see if that user works.