Ask Your Question

Fedora 20 upgrade with fedup 0.8 (ending in yum segfault)

asked 2013-12-20 13:07:46 -0500

updated 2014-02-13 13:49:44 -0500

mether gravatar image

I ran fedup --network 20 last night.

/var/log/fedup.log ends in "... /bin/fedup exiting cleanly ..." so I assume success in downloading all necessary packages. I had already run yum update so everything was looking rosy (I even checked that fedup was at version 0.8).

I rebooted and allowed "system upgrade" to run but when I returned to my laptop it was off. I turned it back on and grub was missing the upgrade entry but it also did not have an entry for F20. So I watched the little Fedora logo fill up and waited a bit thinking "No worries, I'll just check log files and/or rerun fedup and everything will be fine".

I then realised that x was failing to start up. I'm not sure why but I can't startx and get gdm running - I think it may be a graphics driver issue but I'm not certain on this yet.

My solution was to try fedup again but all I got was Segmentation Fault (nothing else). So I tried yum. It turns out that yum is returning these two words no matter what I give it (even "--help"). [edit: I've tried verbose option and it produces nothing more. As root, yum doesn't produce any output at all but it also doesn't do anything either]

So now my yum is not working which means I can't get fedup to run, nor can I fix my xorg issues.

$ rpm -V yum
S.5....T.   c /etc/yum.conf

I've also tried rpm --rebuilddb and the seg fault continues...

I checked the common issues before doing the upgrade but apparently mine is uncommon... Does anyone have any idea what's going on or what I should do?

edit retag flag offensive close merge delete


something's gone very wrong if both fedup and yum are segfaulting. do you have any other OS, or a live image, handy? can you try booting one of those to see if they also have problems?

AdamW gravatar imageAdamW ( 2013-12-20 23:17:54 -0500 )edit

I don't right now - I don't have an optical drive on my laptop so I'm looking into liveusb-creator (which I'll run on this windows machine).

jcuenod gravatar imagejcuenod ( 2013-12-20 23:35:57 -0500 )edit

I think fedup is segfaulting because yum is segfaulting. My issue is that yum --help segfaults. I've tried using rpm -i to install older versions (and even the fc20 version from /var/lib/system-upgrade) but no luck. I ran autrace /usr/bin/yum and got a whole lot of output that I don't know what to do with.

jcuenod gravatar imagejcuenod ( 2013-12-20 23:38:20 -0500 )edit

grepping through autrace output I've found the sigsegv right after two sections with "success=no" which seem to be trying to open something to do with rpm macros. rpm seems to be functioning correctly though (rpm -qa starts listing packages).

jcuenod gravatar imagejcuenod ( 2013-12-21 05:08:16 -0500 )edit

Okay, yes, I have a live image that I can boot off and it's working perfectly - gnome3.10 is interesting. Now what? Is there some way that I can repair the upgrade (which seems to be half-completed)? Is it possible to use rpm to install all the packages in /var/lib/system-upgrade - it seems that not all the packages installed (or something like that)?

jcuenod gravatar imagejcuenod ( 2013-12-21 09:15:03 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted

answered 2013-12-23 08:08:45 -0500

Turns out that the problem was my laptop overheating which sent a warning that caused [dracut?] to stop the upgrade and power off.

That makes sense - sort of but it's really annoying because it made my system nigh unusable.

The solution was to use grub2-install /dev/sda (and grub2-mkconfig -o /boot/grub2/grub.cfg - though I'm not sure that both of these are necessary each time) to put the system upgrade option back into the grub menu and then allow the upgrade to run with a fan pelting my laptop.

It would be really useful if dracut logs were accessible after a power off - it took me babysitting the install and taking a photograph of the screen as something dramatic happened to figure out that there was a power warning buried under a whole lot of other messages (none of which are in any log files I could find).

edit flag offensive delete link more

answered 2013-12-20 14:44:22 -0500

A segmentation fault is a program error (a bug in the program), that usually happens when memory addressing is done incorrectly. If you can find which program is having the error, yum or rpm, you could then try to reinstall that program. You could then also file a bug report at

edit flag offensive delete link more

Question Tools


Asked: 2013-12-20 13:07:46 -0500

Seen: 766 times

Last updated: Dec 23 '13