Bug 595921 - grubby SIGSEGV on kernel installation.
Summary: grubby SIGSEGV on kernel installation.
Alias: None
Product: Fedora
Classification: Fedora
Component: grubby
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-25 22:16 UTC by Maciej Żenczykowski
Modified: 2011-06-27 16:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 16:39:27 UTC
Type: ---

Attachments (Terms of Use)

Description Maciej Żenczykowski 2010-05-25 22:16:25 UTC
I just performed a yum upgrade (after rpm -hvU fedora-release-13) of a (very minimal) Fedora 12 system to Fedora 13.

The upgrade went just fine, with the exception of grubby segfaulting and failing to update grub.conf with the new kernel.

Here's a log of what happens when I uninstall and reinstall the Fedora 13 kernel:

[root@gaia ~]# uname -a
Linux gaia #1 SMP Fri Apr 30 19:46:25 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

[root@gaia ~]# cat /etc/redhat-release 
Fedora release 13 (Goddard)

[root@gaia ~]# yum list extras
Extra Packages
cups-windows.i386                  1:6.0-1                             installed
kernel.x86_64                              installed

[root@gaia ~]# rpm -q kernel

[root@gaia ~]# rpm -e kernel-

[root@gaia ~]# yum upgrade
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0: set to be installed
--> Finished Dependency Resolution

Dependencies Resolved

 Package        Arch           Version                    Repository       Size
 kernel         x86_64           updates          21 M

Transaction Summary
Install       1 Package(s)
Upgrade       0 Package(s)

Total download size: 21 M
Installed size: 103 M
Is this ok [y/N]: y
Downloading Packages:
kernel-                       |  21 MB     06:33     
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Installing     : kernel-                           1/1 
grubby recieved SIGSEGV!  Backtrace (8):
grubby recieved SIGSEGV!  Backtrace (8):

  kernel.x86_64 0:                                              


[root@gaia ~]# cd /boot/grub/

[root@gaia grub]# cat grub.conf 
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd1,0)
#          kernel /vmlinuz-version ro root=/dev/md1 rhgb quiet acpi_enforce_resources=lax
#          initrd /initrd-version.img
password --md5 $1$xxxxxxxx$xxxxxxxxxxxxxxxxxxxxxx
title Fedora (
        root (hd1,0)
        kernel /vmlinuz- ro root=/dev/md1 acpi_enforce_resources=lax SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
        initrd /initramfs-
title Memtest86
        root (hd1,0)
        kernel /memtest86+-4.00
[root@gaia grub]# 


title Fedora (
        root (hd1,0)
        kernel /vmlinuz- ro root=/dev/md1 acpi_enforce_resources=lax SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
        initrd /initramfs-

is missing.

Comment 1 Maciej Żenczykowski 2010-05-26 06:58:07 UTC
The above was with an x86_64 box.
I've now had the exact same thing come up on an i686 install:

# yum upgrade (to F13, otherwise than the error message below the upgrade process is totally smooth and clean - this box was pretty much a virgin [but fully uptodate] F12 install)

  Installing     : kernel-PAE-                     454/934
grubby recieved SIGSEGV!  Backtrace (8):

Comment 2 Maciej Żenczykowski 2010-05-26 07:10:56 UTC
Version of grubby in question (I'll try installing and testing some older versions as well):

# rpm -q grubby

Comment 3 Maciej Żenczykowski 2010-05-26 07:15:19 UTC
Interestingly it turns out I've been running with exactly that version of grubby on an F12 development laptop (with some mesa + kernel packages from F13 for better nvidia support) for a while now, and didn't notice any problems.

Comment 4 Bug Zapper 2011-06-02 13:30:24 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 5 Bug Zapper 2011-06-27 16:39:27 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.