We don’t know exactly what you see when you cannot boot.
However, if you can get the grub menu to display then you should be able to select an older kernel that did boot properly and boot with that.
Once booted it is not super difficult to recover. Let us know if you can boot to an older kernel and we can then step through the repairs.
One critical thing to remember is that when doing an upgrade it is very important to always allow the upgrade to complete and the prompt to return before doing anything else. Then wait an additional 5 to 10 minutes after the upgrade completes before rebooting. This is time required by the system to build the new kernel modules for an upgraded kernel and drivers.
When you get to the grub menu (with the correct entry selected) press e which lets you do one-time edits to that entry. Navigate to the end of the line that starts with linux and add 3 (space and 3) to the end, then press either F10 or ctrl-X
Once you have started in non graphics mode, you can log in and reinstall the Nvidia driver. There are different things you could append to that line if logging in is an issue (you can make it comes up already root, rather than requesting log in): search for instructions for resetting the root password.
The 3 is a shorthand for a more complicated incantation. Online instructions advise to use the full incantation rather than the 3. In some future version that might make a difference. But for now using just the 3 works fine.
I managed to get access to the system via no-graphics mode. Thanks to that, i reinstalled nvidia drivers by your instructions. Unfortunately, this time it’s not the case. Users still not listed in the graphics-mode.
I noticed a lots of error like unable to enumarate usb device, usb descriptor errors during booting and shutting down. Also this Gdm: Failed to list cached users: GDBus.Error:org.freedesop.Dbus.Error.NameHasNoOwner strange error.
Maybe the best way to fix - once again reinstall system, but install drivers in no-graphics mode.
That sounds like an unrelated problem that you might ignore or might want to look into later.
That sounds like THE problem.
That Gdm problem certainly sounds like one that could be solved by a reinstall. That seems like an excessively drastic solution to me. I expect there is some simple config file that could be delete or edited to fix the problem (nano is a good non-gui editor for those of us who only know how to use gui editors).
I don’t use Gdm, so I can’t guess what config file(s) to fix. So hopefully you get a better answer soon. Meanwhile I think reinstalling should work but shouldn’t be needed.
From many painful experiences that needed reinstall of drivers for old Nvidia cards (or other corrections needed due to those cards), I can tell you for certain that in some of those situations you can get to a terminal that way after a failed attempt at launching the GUI and in some you can’t. When that method of getting to a terminal fails, you need to know how to get directly there from grub (which I hope I explained correctly in an earlier post in this thread). Sometimes the terminal only works if you have not yet tried to start the GUI.
For the USB errors the starting point is to disconnect all usb devices while booting then reconnect them one at a time to see if one can identify which is triggering the errors.
The dbus error is beyond my expertise.
One should always be able to use ctrl-alt-F3 (or F4, F5 or F6) to open a text login screen after the boot has completed. That should allow installing drivers or other packages needed without the graphical DE available.
I decieded to check my strationary PC, which also runs by Fedora and this is jourantctl -u gdm:
Feb 21 22:10:23 mikhail-pc-linux systemd: Starting gdm.service - GNOME Display Manager...
Feb 21 22:10:23 mikhail-pc-linux systemd: Started gdm.service - GNOME Display Manager.
Feb 21 22:11:24 mikhail-pc-linux gdm-password]: gkr-pam: unable to locate daemon control file
Feb 21 22:11:24 mikhail-pc-linux gdm-password]: gkr-pam: stashed password to try later in open session
Feb 21 22:11:30 mikhail-pc-linux gdm: Gdm: Child process -1708 was already dead.
Feb 22 00:13:40 mikhail-pc-linux systemd: Stopping gdm.service - GNOME Display Manager...
Feb 22 00:13:41 mikhail-pc-linux gdm: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: activation request failed: a >
Feb 22 00:13:41 mikhail-pc-linux systemd: gdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 22 00:13:41 mikhail-pc-linux systemd: gdm.service: Failed with result 'exit-code'.
Feb 22 00:13:41 mikhail-pc-linux systemd: Stopped gdm.service - GNOME Display Manager.
Feb 22 00:13:41 mikhail-pc-linux systemd: gdm.service: Triggering OnFailure= dependencies.
Feb 22 00:13:41 mikhail-pc-linux systemd: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (lvm2-monitor.service has 'stop' >
So, as you can see there are the GDBus error, but on stationary PC Fedory boots so quickly, that i even can’t spot loading screen. Basicly logs on laptop the same, except gdm-password loss. Maybe this is the problem, the accountService. I tried to reinstall accountService but no effect.