I solved this myself but wanted to document the solution in case other users might have the same issues. All hints and feedback on how to best achieve this goal are appreciated.
Issue
The upgrade itself ran smooth but after boot there is just a blinking cursor, no login screen.
Debugging steps (feel free to skip)
Switch to a text console (Ctrl+Alt+F3), login as prompted.
Check for failed services systemctl --failed
Some user@[somenumber].service entries were listed
systemctl status user@[somenumber].service can give first hints, but I decided to check the full journal at this point.
journalctl -b gives you the logs from the current boot. (Iām currently reconstructing this using journalctl -b -1, very convenient, thanks journalctl! )
Quickly scroll through using the pagedown key, red stack traces appear near the end, starting with a systemd-coredump[1612]: [š”] Process 1596 (gnome-session-i) of user 60578 dumped core. That doesnāt look good!
Scrolling up a bit there are some useful hints:
systemd\[1\]: Starting user@60578.service - User Manager for UID 60578ā¦
dbus-broker-launch\[1109\]: Activation request for āorg.freedesktop.home1ā failed: The systemd unit ādbus-org.freedesktop.home1.serviceā could not be found.
unix_chkpwd\[1572\]: could not obtain user info (gdm-greeter)
unix_chkpwd\[1574\]: could not obtain user info (gdm-greeter)
(systemd)\[1557\]: user@60578.service: PAM failed: Authentication service cannot retrieve authentication info
(systemd)\[1557\]: user@60578.service: Failed to set up PAM session: Operation not permitted
(systemd)\[1557\]: user@60578.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
systemd\[1\]: user@60578.service: Main process exited, code=exited, status=224/PAM
systemd\[1\]: user@60578.service: Failed with result āexit-codeā.
systemd\[1\]: Failed to start user@60578.service - User Manager for UID 60578.
Switch to a text console (Ctrl+Alt+F3), login as prompted.
Check your current status of authselect: authselect current
If it says No existing configuration detected. then this issue is for you!
If it starts with Profile ID: then the following is unlikely to help you, sorry
Setup with the default authselect configuration or read more about authselect in the documentation or the two great magazine articles Iāll link below. sudo authselect select local with-silent-lastlog with-mdns4 --force
Reboot systemctl reboot The login screen should be back now
Update: Some users mentioned that a second reboot was necessary.
Thank you so much for this! After about 6 hours of googling I got Fedora 43 graphical login working. This is emblematic of new user frustration with Linux. Iāve been using Linux for about 28 years and without this posting Iād still have a broken Linux update. Perhaps I could have solved this sooner after poring over logs but I doubt it. This really just shouldnāt happen in this day and age, but unfortunately I donāt have any suggestions for preventing it.
Thank you so much for this! This was the problem with my laptop, so I have marked my own thread as solved and posted a link here. Thank you; I had tried so many things and nothing had worked.
It would have been so bad if authselect wasnāt so confusing. There are warnings everywhere not to edit files, but there isnāt any documentation about how to configure modules that are not pre-defined āfeaturesā. My system is up, again, with a custom profile; that was easy. But, now Iām stuck.
For special needs, you can create your own profile using authselect create-profile. Run man authselect to see the man page and search for ācreate-profileā.
For example
sudo authselect create-profile myprofile -b local
Then edit the files in /etc/authselect/custom/myprofile and the use authselect select custom/myprofile to enable it.
Iām surprised you wouldnāt have just reinstalled.
I have less experience (Ubuntu 6.06), but seen update issues back then, had some with Windows before that, and by the time Vista SP1 came out I knew not to bother with major OS version upgrading: I can back up and set-up a new install sooner than I can track-down random issues
Thanks. Thatās where I was headed, but it doesnāt say those files are editable anywhere in the documentation, while everywhere else it just says DO NOT EDIT.
Iām glad that this already helped a hand full of users who commented here (and probably a few more who didnāt), seems like my time writing it was well spent
While there are surely interesting use cases for custom authselect features, Iād ask you, @prdamon, to create a separate discussion for that. It might be beneficial for interested parties of both sides to not have this special topic mixed with the āargh, canāt login after I upgraded!?ā folks for whom I specifically created this thread. Links back and forth are always appreciated of course
One thing that could be discussed here, however is this thought in the back of my mind: Could we as the Fedora community have done something to prevent people running into this issue? Is there something we still can do? Would it be worth the effort and what would be the first steps?
If you create your own profile, you can modify it to exactly the way you want. Or you could opt-out of using authprofile, and edit the files in /etc/pam.d. However, if you do so, you also need to make manual updates when and if needed.
I was thinking while I was having the problem, āI am definitely going to download those ālarge filesā and let my laptop report bugs to Fedora in future, because they definitely donāt have anyone else with this sort of laptop to report problems.ā I had the issue a couple of months ago where kernel 6.16 kept disconnecting my WiFi as well, so there have now been two disasters in rapid succession. In the eight years Iāve used Fedora before that, the worst thing that ever happened was when an update deleted my desktop wallpaper. Iām not going to be any use at actually contributing, so weāll still need experts like you, but I think getting more peopleās systems to test the updates on will help provide more feedback before these updates go public. If everyone who uses Fedora gets more involved in the community, it might not even matter that users like me donāt know anything about maintaining an operating system
Since my upgrade from FC42 to FC43 I have read many replies.
From David Auer I have read:
Solution
Switch to a text console (Ctrl+Alt+F3), login as prompted.
Check your current status of authselect: authselect current
If it says No existing configuration detected. then this issue is for you!
After Ctrl+Alt+F3 I can read: activate the web controle with: systemctl enable --now cockpit.socket
Until now I did not do it.
Can I also use this command later in the Wayland terminal window?
After login I tried: gastonv@localhost:~$ authselect current Identificatiecode van profiel: sssd Aangezette functies: (translated: started functions) - with-fingerprint - with-silent-lastlog - with-mdns4
Thus it was not:
If it says No existing configuration detected. then this issue is for > you!
Thus I have not to use it.
Then after the following command I and my password, I can start and work as before in Wayland: gastonv@localhost:~$ gnome-shell --wayland
Please my question: with these notes, in my case, should there be a solution in order to run Wayland directly?
Then please a second question:
On right top of Wayland, when I click the Settings gear icon, nothing is to see.
And I do not see a button in order to close and exit the sesion.
Therefore I use: gastonv@localhost:~$ shutdown -P now
Awaiting, many thanks in advance for each answer.
Kind regards,
Gaston Verhulst.
I donāt see how your questions are related to this thread and I canāt answer them, sorry. Please try to stay on topic and create a new thread when in doubt.
I have read your comment and because your topic was marked as Solved, then I shall create a new topic. Very sorry that I have made that reply to this topic.
Kind regards,
Gaston Verhulst
thanks for posting this solution, would never have solved it myself, been upgrading since fc20 and was in the same boat, thought it was nvidia drivers, then xorg then gnome, saved me allot of time.
Dear David Auer,
Very sorry and excusing that I answer on your last reply if my answer is not on the right place.
Every day I start with a black screen and my login command: gastonv@localhost:~$ gnome-shell --wayland
Reading the top post again, I have tried: $ systemctl -- failed UNIT LOAD ACTIVE SUB DESCRIPTION systemctl current authselect current Identificatie van profil: sssd > Identification from profile: sssd Aangezette functies: > started functions: with-fingerprint with-silent-lastlog įŗith-mdns4
Backup is opgeslagen > stored in Profiel > Profile "local" werd geselecteerd > becomed selected $ systemctl reboot
I am very sorry that the result were a black screen again.
But at the end I was happy I could restart with: $ gnome-shell --wayland
So I can work in Fedora 43.
Perhaps I have made a failure?
Many thanks in advance for each answer.
Kind regards,
Gaston Verhulst.
Yes! ā People with very old, very new, or one-of-a-kind systems that linux developers are unlikely to use should be encouraged to participate in pre-release testing. Before retiring, I often encountered issues with missing or changed numerical libraries used by my software that would not be detected if I simply updated, so always tested on fresh installs.
)
