Bug 909700 - yum: terminates with SIGBUS during package installation
Summary: yum: terminates with SIGBUS during package installation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-10 15:12 UTC by Mikolaj Izdebski
Modified: 2014-02-05 19:05 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:05:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
GDB backtrace of yum process (40.91 KB, text/plain)
2013-02-10 15:12 UTC, Mikolaj Izdebski
no flags Details
yum output on stdout/stderr (222.02 KB, text/plain)
2013-02-10 15:13 UTC, Mikolaj Izdebski
no flags Details
versions of dependencies of yum (2.57 KB, text/plain)
2013-02-10 15:14 UTC, Mikolaj Izdebski
no flags Details

Description Mikolaj Izdebski 2013-02-10 15:12:03 UTC
Description of problem:
When installing packages yum dumps core terminated by signal 7 (SIGBUS). The core dump occurs after all packages are installed, but before they are verified. This is probably a bug in one of libraries YUM depends on, but I'll leave further investigation for you.

Version-Release number of selected component (if applicable):
yum-3.4.3-49.fc18.noarch

How reproducible:
I could reproduce reliably, but only with some sets of packages to install.

Steps to Reproduce:
1. yum --nogpgcheck --assumeyes --noplugins --releasever=rawhide --installroot /home/kojan/vmock/root install @buildsys-build maven-local
  
Actual results:
yum process was killed with signal 7 (core dumped).

Expected results:
package installation proceeds without core dumps

Additional info:
will be attached

Comment 1 Mikolaj Izdebski 2013-02-10 15:12:55 UTC
Created attachment 695786 [details]
GDB backtrace of yum process

Comment 2 Mikolaj Izdebski 2013-02-10 15:13:36 UTC
Created attachment 695787 [details]
yum output on stdout/stderr

Comment 3 Mikolaj Izdebski 2013-02-10 15:14:49 UTC
Created attachment 695788 [details]
versions of dependencies of yum

Comment 4 Fedora End Of Life 2013-12-21 11:18:29 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 5 Fedora End Of Life 2014-02-05 19:05:10 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.