Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: grubby crashed while rerunning the install script to pick up a dracut config change. Version-Release number of selected component (if applicable): grubby-8.37-1.fc22.i686 How reproducible: Not sure Actual results: bash-4.3# /bin/kernel-install add 4.0.0-0.rc5.git4.1.fc23.i686+PAE /boot/vmlinuz-4.0.0-0.rc5.git4.1.fc23.i686+PAE grubby fatal error: unable to find a suitable template *** Error in `/sbin/grubby': free(): invalid pointer: 0x09557679 *** ======= Backtrace: ========= /lib/libc.so.6(+0x6ddf3)[0xb7588df3] /lib/libc.so.6(+0x75e0c)[0xb7590e0c] /lib/libc.so.6(cfree+0x50)[0xb75953c0] /sbin/grubby[0x8051634] /sbin/grubby[0x804c7fc] /lib/libc.so.6(__libc_start_main+0xf7)[0xb7533797] /sbin/grubby[0x804c883] ======= Memory map: ======== 08048000-08057000 r-xp 00000000 fd:00 932786 /usr/sbin/grubby 08057000-08058000 r--p 0000e000 fd:00 932786 /usr/sbin/grubby 08058000-08059000 rw-p 0000f000 fd:00 932786 /usr/sbin/grubby 09557000-09578000 rw-p 00000000 00:00 0 [heap] b7513000-b7515000 rw-p 00000000 00:00 0 b7515000-b7519000 r-xp 00000000 fd:00 923892 /usr/lib/libuuid.so.1.3.0 b7519000-b751a000 r--p 00003000 fd:00 923892 /usr/lib/libuuid.so.1.3.0 b751a000-b751b000 rw-p 00000000 00:00 0 b751b000-b76ec000 r-xp 00000000 fd:00 958073 /usr/lib/libc-2.21.90.so b76ec000-b76ee000 r--p 001d0000 fd:00 958073 /usr/lib/libc-2.21.90.so b76ee000-b76ef000 rw-p 001d2000 fd:00 958073 /usr/lib/libc-2.21.90.so b76ef000-b76f2000 rw-p 00000000 00:00 0 b76f2000-b76fe000 r-xp 00000000 fd:00 954183 /usr/lib/libpopt.so.0.0.0 b76fe000-b76ff000 r--p 0000b000 fd:00 954183 /usr/lib/libpopt.so.0.0.0 b76ff000-b7700000 rw-p 0000c000 fd:00 954183 /usr/lib/libpopt.so.0.0.0 b7700000-b7741000 r-xp 00000000 fd:00 946547 /usr/lib/libblkid.so.1.1.0 b7741000-b7743000 r--p 00041000 fd:00 946547 /usr/lib/libblkid.so.1.1.0 b7743000-b7744000 rw-p 00043000 fd:00 946547 /usr/lib/libblkid.so.1.1.0 b7744000-b7745000 rw-p 00000000 00:00 0 b77a0000-b77bc000 r-xp 00000000 fd:00 931477 /usr/lib/libgcc_s-5.0.0-20150319.so.1 b77bc000-b77bd000 r--p 0001b000 fd:00 931477 /usr/lib/libgcc_s-5.0.0-20150319.so.1 b77bd000-b77be000 rw-p 0001c000 fd:00 931477 /usr/lib/libgcc_s-5.0.0-20150319.so.1 b77be000-b77c0000 rw-p 00000000 00:00 0 b77c0000-b77c2000 r--p 00000000 00:00 0 [vvar] b77c2000-b77c3000 r-xp 00000000 00:00 0 [vdso] b77c3000-b77e7000 r-xp 00000000 fd:00 954092 /usr/lib/ld-2.21.90.so b77e7000-b77e8000 r--p 00023000 fd:00 954092 /usr/lib/ld-2.21.90.so b77e8000-b77e9000 rw-p 00024000 fd:00 954092 /usr/lib/ld-2.21.90.so bf8f9000-bf91b000 rw-p 00000000 00:00 0 [stack] grubby fatal error: unable to find a suitable template grubby: doing this would leave no kernel entries. Not writing out new config.
Please attach the grub.cfg that this happens with.
I have an empty grub.cfg file as I still use grub for booting not grub2.
Created attachment 1014075 [details] /boot/grub/grub.conf with md5 hash replaced Maybe there is a problem parsing my grub.conf file rather than the empty grub.cfg file. The effect of the crash is that I get new kernel entries in grub.conf, but without the initrd line. I need to add that manually to be able to boot new kernel entries.
grubby-8.39-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/grubby-8.39-1.fc22
grubby-8.40-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/grubby-8.40-1.fc22
Package grubby-8.40-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing grubby-8.40-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-6243/grubby-8.40-1.fc22 then log in and leave karma (feedback).
I didn't test the f22 version, but the rawhide version is working for me now. Thanks!
grubby-8.40-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.