|Summary:||[abrt] crash in coreutils-7.6-11.fc12: elf_machine_rela: Process /bin/su was killed by signal 11 (SIGSEGV)|
|Component:||prelink||Assignee:||Jakub Jelinek <jakub>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||12||CC:||jakub, kdudka, ovasik, schwab, tmraz, twaugh|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-12-03 13:20:19 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description colinmw 2010-07-10 11:11:15 UTC
abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: su - popacc component: coreutils crash_function: elf_machine_rela executable: /bin/su global_uuid: 48697ce2f7df02eeb8dd64b31d4659a8ba8720ff kernel: 18.104.22.168-127.fc12.x86_64 package: coreutils-7.6-11.fc12 rating: 1 reason: Process /bin/su was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Comment 2 Ondrej Vasik 2010-07-10 11:47:39 UTC
From the backtrace it seems that the issue is not located directly in su. Was the crash after waking up from hibernate? Is there something specific on the system?
Comment 3 Ondrej Vasik 2010-07-10 18:00:13 UTC
As there is PAM involved in the backtrace, adding Tomas Mraz to cc...
Comment 4 Tomas Mraz 2010-07-12 07:48:51 UTC
It seems that the crash happens in the glibc when the pam_fprintd module is dlopened. I don't see anything weird in the PAM call however the debuginfo is missing for the pam package.
Comment 5 colinmw 2010-07-12 11:02:52 UTC
I don't believe the machine was in a 'hibernate' state as it is a desktop machine. There is nothing special about the hardware or software to my knowledge, it's just running FC12 executables. I'll add debuginfo for pam just in case it happens again.
Comment 6 Ondrej Vasik 2010-07-12 14:36:00 UTC
moving to glibc...
Comment 7 Bug Zapper 2010-11-03 12:08:31 UTC
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 8 Bug Zapper 2010-12-03 13:20:19 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.