Ask Your Question

Fedora 29 upgrade hangs after reboot

asked 2019-02-02 10:42:33 -0500

Orriginal gravatar image

Fedora 29 upgrade hangs after reboot and never reach's the log in screen

I waited untill I figureed the 29 release was stable and upgraded via the "notice" at the top of the screen once I had done the latest dnf upgrade on my 28 workstation

The upgrade appeared to go with no errors but once completed and rebooted, it hangs. I have managed a number of times now to go in via the previous option on the bootup screen which is listed as Fedora 28 and get informed the upgrade was successful once I log in

I have logged in a su in terminal and tried to do a dnf update but get

dnf update -y
Config error: Parsing file "/etc/dnf/dnf.conf" failed: IniParser: Missing '=' at line 4

Any ideas please would be gratefully received Thanks in advance

edit retag flag offensive close merge delete


inrthe LOG VIEWER - I get the following under "important"

17:29:29 systemd: Failed to start dnf makecache.
17:23:54 gnome-session-b: GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed
17:23:52 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
17:23:04 reporter-system: System encountered a non-fatal error in __check_object_size()
Orriginal gravatar imageOrriginal ( 2019-02-02 10:55:33 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted

answered 2019-02-03 05:07:48 -0500

Orriginal gravatar image

updated 2019-02-03 07:19:07 -0500

hhlp gravatar image

It seems that during the update, something had interrupted the install as the dnf.conf file had been written with errors and also some Modules had become corrupted. At first, I was unable to do a dnf update when I had booted into a previous install that was listed as 28 but in fact was 29 ( !) - error was

dnf update -y Config error: Parsing file "/etc/dnf/dnf.conf" failed: IniParser: Missing '=' at line 4

the dnf.conf file had been written as

/bin/bash: q: command not found

( I had NOT used vi or anything to rdit the file previously) I rewrite as ( with help from someone on here )


Once this had been re written it managed to boot in to 29..very slowly the first time as it updated modules and I ran dnf update The dnf update listed connection to sisco which I had never seen before

Fedora 29 openh264 (From Cisco) - x86_64 182 B/s | 543 B 00:02 etc etc

After this, it has booted into the Fedora 29 on grub with no errors but fairly slowly but seems to be getting quicker... NO idea what happened but thanks to all for the help and suggestions

edit flag offensive delete link more

answered 2019-02-02 10:56:38 -0500

loboedu gravatar image

Do you have any dkms packages installed on your f28? Maybe you'll have to reinstall such packages.

Also, have you tried removing the 'quiet' option from the grub file from the grub load screen, so you can see where the boot process is stalling? If you have, please post here, it should hell understand the problem.

edit flag offensive delete link more


Got to admit to not knowing what a dkms package is but as far as I can remember, my Fed 28 was pretty basic really....As for the grub.. I'll see if I can do that and then report back...

Orriginal gravatar imageOrriginal ( 2019-02-02 11:41:31 -0500 )edit

If you don't know what dkms stands for, then indeed there must not be any installed.

This grub thing (I don't know if you know): at the grub selection screen, press "e" over the keernel version you want and then edit the file removing the option "quiet" from the line that starts with "linuzvm..."

loboedu gravatar imageloboedu ( 2019-02-02 12:01:25 -0500 )edit

So, pressed e ( thanks for that ) on the Ver 29 line and looked through the lines, searching fo rlinuzvm" and did not find one anywhere...I also looked through the ver 28 boot for th e same and did not find it...but I did find "quiet" in a line beginning with linux16, that had rhgb quiet nouveau - so i deleted quiet.................and rebooted...........and it all went through and went to the 3 dots on the screen and after a long time, once again, it went red and I am none the wiser as to why it stopped.....any more Ideas ?

Orriginal gravatar imageOrriginal ( 2019-02-02 12:49:10 -0500 )edit

typo above.. I looked for what you suggested, linuzvm, and did not find it...

Orriginal gravatar imageOrriginal ( 2019-02-02 13:34:04 -0500 )edit

"quiet" in a line beginning with linux16, that had rhgb quiet nouveau" That was it!

The idea of removing this quiet thing was to see in where the boot process stalls. What are the last lines to appear?

loboedu gravatar imageloboedu ( 2019-02-02 16:34:42 -0500 )edit

Question Tools

1 follower


Asked: 2019-02-02 10:42:33 -0500

Seen: 530 times

Last updated: Feb 03 '19