Fedora fails to boot after updating a Fresh Install

I decided to give fedora a try after using bazite for a few months. I installed on a clean and fresh fully formatted drive. Fedora was installed via live usb environment. I got into the os and there was over 1,000 pending updates in discover totaling 5.5GB. I approved install of updates. Restarted and got back into the OS I then began my usual curiosity and poked and prodded around your OS to get a feel for what was going. I removed handful of pre installed apps that I knew I would never use. I installed apps that I was going to use from discover. I added a few repos that were PRE CONFIGURED in the discover settings and checked the repo box for nvidia as I have an nvidia gpu installed. I then was unable to get the pc to shut down via the GUI like repeatedly pressing them provided no response or pop up or prompt. I then shut down via my case shut down button. Turned it back on and nothing, black screen no matter what boot option chosen in grub. This is a major issue and should be resolved promptly. How do you want people to use your OS when this is the out of the box experience. I am fairly tech savvy and consider myself a power user and this happens. You will never get widespread adoption from the general public if this is the experience and I in good faith cannot recommend this OS to friends and family who express to me that they want to ditch windows. Please provide me with an explanation of what went wrong, why it went wrong, and what you have done to mitigate against this for future users. Thank you have a nice day.

When reporting an issue you need to provide enough detail to allow others with similar hardware to reproduce the issue. For the most part, Fedora just packages what is available from upstream, so it is important to capture details that can be passed to the appropriate upstream devs. The first step is to press Esc when booting to see messages.

If you have time, you can also view the journal on the installed system using the Live USB and a terminal:

  1. if you are not familiar with journalctl, read https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/
  2. mount the drive, e.g., using Gnome disks
  3. find the journal directory DIR=…/var/log/journal/[long random name/.
  4. run journalctl --directory=DIR … where … is “filters” that select relevant entries.

If you need to a quick fix, you can copy the journal directory to another storage device for future reference and then try using an updated “respin” installer from https://dl.fedoraproject.org/pub/alt/live-respins/. You should also make sure you have current vendor firmware updates.

2 Likes

With all due respect. I am not going to track down all the logs for you. I am not doing your job for you. its community built whatever. You are providing an operating system it is a consumer product regardless. I have better things to do with my time. I am not QA for fedora. I explained to you what happened. I will not sit here and dig through your operating system to find your bug reports. I am certain that on the back-end somewhere the package maintainers have access to the data and the pings my account made to their repositories and so on. If they want to fix the problem they can but I will not go any further than reporting my issue here as it was reported. That drive was swiftly formatted and a new Linux Distro installed on top of yours so the likelihood of recovering those logs is slim to none if I even wanted to dig and provide them for you anyways which I don’t. Take my post at face value, do something about it, delete it, makes no difference to me. its yalll’s OS. Yalls reputation, yalls responsibility not mine. Have a nice day.

This is not our job. You might want to read the conditions under which Fedora (and most free open source OS) are provided.

We have no obligation to work for you for free, read your logs, etc.

I close this. Feel free to start from scratch with an approach that contains some respect for those who provide their service for free. And you might want to read in advance our code of conduct, and the conditions under which you use this product for free.

If you want the guarantee that this is the job of others, you need to get a paid subscription (which we don’t offer).

1 Like

This comment (and your entire post) is very disrespectful, and it fails to allow for the FACT that only the user can find and provide logs from THEIR MACHINE.

1 Like