Hi all,

this tutorial https://www.linuxquestions.org/quest...-a-4175700888/ tweaked my interest and I decided to upgrade a F34 VM to the beta.

This is the normal path I use to upgrade my Fedora boxes - one PC with 3 VMs underneath - although I haven't tried a beta in a while. Everything went to plan although I did not watch all of the final bit after "dnf system-upgrade reboot". This had reached 46% when I stopped watching. When I came back to the PC I was presented with the login prompt.

Whoops, when F35 comes up I attempt to login I get "Failed to Start Session". Same if I attempt to login as root. I should point out this is the GUI login.

I guess this is all part of the fun of the beta. For the record:

• F34 was up to date before the upgrade
• This is the xfce spin
• I'll also note that files were backed up - this VM has a minimal footprint so is easy recoverable.

It would be good to revive the system though. I am faced with a login prompt. Is there any way I can fall back to the command line and hopefully install some updates?

TIA

You will probably get a better answer on the askfedora forum. They are almost exclusively focused on fedora there.

With that said, you might use the grub menu and by editing the linux command line in grub be able to boot to single user mode, verify that you are actually at release 35, then do the updates.

I know that fedora by default hides the grub menu during boot.
If the grub menu is hidden during boot you can, by giving the VM window focus before you power it on, hold down the shift key during boot and it should display the grub boot menu so you can select the entry and choose to edit the grub entry before boot.

1 members found this post helpful.

When this happens to me I normally just wait a day or more and do an ordinary dnf upgrade hoping whatever broke the login manager already got found and fixed. If ambitious and anxious, I look to see if a bug about it has already been reported, and if really ambitious and anxious and didn't find one, I create a bug report about it.

Thanks for the help. This is a useful learning exercise. I am going step by step. Currently in single user mode (believe me that is an achievement for me). I'll keep plugging away and see how I go.

Not yet solved but moving forward.

Cheers

No real solutions. I fell back to the CLI which was mostly okay for my purposes. This prompted me to do a barebones Fedora install. I also did a mionimal Centos install for another VM I use so a couple of smaller footprints to live with. I'll call that a win