Bug 599962
| Summary: | segfault in grubby | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Neal Becker <ndbecker2> | ||||||||
| Component: | grubby | Assignee: | Brian Lane <bcl> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 13 | CC: | bcl, nerijus, pjones | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2010-06-07 22:59:37 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Neal Becker
2010-06-03 21:07:57 UTC
Created attachment 420666 [details]
anacond.log
Created attachment 420685 [details]
upgrade.log
Created attachment 420702 [details]
grub.conf
rpm -q kernel grubby kernel-2.6.33.5-112.fc13.x86_64 grubby-7.0.13-1.fc13.x86_64 Relevant part of the log is the backtrace: grubby recieved SIGSEGV! Backtrace (9): /sbin/grubby[0x40805f] /lib64/libc.so.6(+0x32a40)[0x7f031b820a40] /lib64/libc.so.6(+0x1279ba)[0x7f031b9159ba] /sbin/grubby[0x40695e] /sbin/grubby[0x406b10] /sbin/grubby[0x406d6d] /sbin/grubby[0x407ec5] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7f031b80cc5d] /sbin/grubby[0x401709] This may be related to the suitableImage() bug I just fixed. The grub.conf you posted is from a f13 system. Do you still have the f12 version that failed? No, but all I changed is edit the version numbers. *** This bug has been marked as a duplicate of bug 592294 *** |