Bug 677050

Summary: [abrt] smart-1.3.1-66.fc15: int_dealloc: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: STEVEN WARD <stevenward666>
Component: smartAssignee: Axel Thimm <axel.thimm>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: axel.thimm
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:887526fa080335b64ff8e03f180b6b9fc9b0d954
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 13:37: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 Flags
File: backtrace none

Description STEVEN WARD 2011-02-12 23:25:03 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 73807 bytes
cmdline: /usr/bin/python /usr/bin/smart fix
comment: I keep getting a segmentation fault using yum. I've tried to install the missing debuginos that abrt requires,but for some reason it gets me to the KDM login screen.
component: smart
Attached file: coredump, 18157568 bytes
crash_function: int_dealloc
executable: /usr/bin/python
kernel: 2.6.38-rc2+
package: smart-1.3.1-66.fc15
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1297552816
uid: 0

How to reproduce
-----
1.Log into Fedora Rawhide.
2.Log into yum
3.yum install smart and use it

Comment 1 STEVEN WARD 2011-02-12 23:25:08 UTC
Created attachment 478409 [details]
File: backtrace

Comment 2 Axel Thimm 2011-04-09 08:51:24 UTC
Can you reproduce it? I hope it was a rawhide hickup back then, my chrooted rawhide doesn't bail out like that ATM. Thanks!

Comment 3 Fedora End Of Life 2013-04-03 13:47:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 STEVEN WARD 2014-06-16 11:11:09 UTC
Hi there, I have switched distributions, so I'm currently on Gentoo now.

Thank you.

Comment 5 Fedora End Of Life 2015-01-09 16:33:45 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 6 Fedora End Of Life 2015-02-17 13:37:52 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.