Version-Release number of selected component: efibootmgr-0.7.0-3.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: efibootmgr -v crash_function: unparse_media_hard_drive_path executable: /usr/sbin/efibootmgr kernel: 3.14.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #5 unparse_media_hard_drive_path at src/lib/unparse_path.c:349 #6 unparse_media_path at src/lib/unparse_path.c:368 #7 unparse_path at src/lib/unparse_path.c:478 #8 show_boot_vars at src/efibootmgr/efibootmgr.c:680
Created attachment 921582 [details] File: backtrace
Created attachment 921583 [details] File: cgroup
Created attachment 921584 [details] File: core_backtrace
Created attachment 921585 [details] File: dso_list
Created attachment 921586 [details] File: environ
Created attachment 921587 [details] File: limits
Created attachment 921588 [details] File: maps
Created attachment 921589 [details] File: open_fds
Created attachment 921590 [details] File: proc_pid_status
Created attachment 921591 [details] File: var_log_messages
Another user experienced a similar problem: Run efibootmgr -v reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: efibootmgr -v crash_function: unparse_media_hard_drive_path executable: /usr/sbin/efibootmgr kernel: 3.15.6-200.fc20.x86_64 package: efibootmgr-0.7.0-3.fc20 reason: efibootmgr killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Simply executed 'sudo efibootmgr -v'. Without '-v', it does not crash. The command used to work a few weeks ago just fine, and I haven't made any UEFI changes since then. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: efibootmgr -v crash_function: unparse_media_hard_drive_path executable: /usr/sbin/efibootmgr kernel: 3.16.3-200.fc20.x86_64 package: efibootmgr-0.7.0-3.fc20 reason: efibootmgr killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Updated FAF report: https://retrace.fedoraproject.org/faf/reports/455801/
Might be caused by https://admin.fedoraproject.org/updates/FEDORA-2014-12419/efivar-0.13-1.fc20 -- that's what I updated a short time ago.
No, it's not caused by that - it's a legitimate efibootmgr bug, and you're just getting a slightly different memory map when the different library is loaded, and that's causing it to fault instead of continue silently in error.
efibootmgr-0.10.0-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/efibootmgr-0.10.0-1.fc21
efibootmgr-0.10.0-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/efibootmgr-0.10.0-1.fc20
efibootmgr-0.10.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/efibootmgr-0.10.0-1.fc19
Package efibootmgr-0.10.0-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing efibootmgr-0.10.0-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13354/efibootmgr-0.10.0-1.fc20 then log in and leave karma (feedback).
Thanks, the new build fixes the crash for me.
efibootmgr-0.11.0-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
efibootmgr-0.11.0-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.