| Summary: | [abrt] yum-3.2.28-5.fc13: elf_dynamic_do_rel: Process /usr/bin/python was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | alon <dotanalon> | ||||
| Component: | glibc | Assignee: | Andreas Schwab <schwab> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 13 | CC: | dmalcolm, ffesti, flokip, fweimer, ivazqueznet, jakub, james.antill, jonathansteffan, maxamillion, pmatilai, schwab, tla | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:6758e15918cff45b3a4a68389c489e45200be97c | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-27 11:49:52 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
alon
2011-04-13 19:50:27 UTC
Created attachment 491892 [details]
File: backtrace
Thanks for filing this bug report. How reproducible is this problem? Is this running on "bare metal", or as the guest OS on a hypervisor? What is the output of running the following command: rpm -qa python python-libs binutils glibc yum rpm rpm-python Looking at the backtrace, there appears to be a failure deep within the call to dlopen (frame 8) of /usr/lib/python2.6/site-packages/rpm/_rpmmodule.so (when yum imports rpm._rpm) Reassigning component to "glibc" in the hope of further insight. hey dave and thanks to the respond, the system runs on dell inspiron 1515 "metal" the problem occur yum I invoked "sudo yum update" the output of the rpm commend is: "python-2.6.4-27.fc13.i686 python-libs-2.6.4-27.fc13.i686 glibc-2.12.2-1.i686 yum-3.2.28-5.fc13.noarch rpm-4.8.1-2.fc13.i686 binutils-2.20.51.0.2-20.fc13.i686 rpm-python-4.8.1-2.fc13.i686" *** Bug 696309 has been marked as a duplicate of this bug. *** Thanks for the information. What is the output of running this command: rpm -V python python-libs binutils glibc yum rpm rpm-python [The only duplicate of this bug so far seems to be on the same machine, so perhaps something has gone wrong on that machine] the output: prelink: /bin/rpm: at least one of file's dependencies has changed since prelinking S.?...... /bin/rpm prelink: /usr/bin/rpm2cpio: at least one of file's dependencies has changed since prelinking S.?...... /usr/bin/rpm2cpio you want to share with me what you trying to find out? (In reply to comment #6) > the output: > prelink: /bin/rpm: at least one of file's dependencies has changed since > prelinking > S.?...... /bin/rpm > prelink: /usr/bin/rpm2cpio: at least one of file's dependencies has changed > since prelinking > S.?...... /usr/bin/rpm2cpio Thanks for this information. > you want to share with me what you trying to find out? "-V" means "verify": my hunch was that somehow one of the libraries was corrupt (given that this problem seems to be unique to this system). But looking at the output, nothing strikes me as out of place. Hopefully the glibc maintainer can suggest further approaches to debugging this. I used update test an updateed only pygtk2 pygtk2-libglade yumex crash yum downgrade pygtk2 pygtk2-libglade is a fix for me (In reply to comment #8) > I used update test an updateed only pygtk2 pygtk2-libglade > yumex crash > yum downgrade pygtk2 pygtk2-libglade > is a fix for me Are you sure this is the same crash, yumex does use pygtk, but yum do not ! >Are you sure this is the same crash, yumex does use pygtk, but yum do not ! no See Bug 697183 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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. |