Bug 663728

Summary: [abrt] hardinfo-0.5.1-2.fc12: lup_solve: Process /usr/bin/hardinfo was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Steve <bugzilla>
Component: hardinfoAssignee: Adel Gadllah <adel.gadllah>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: adel.gadllah
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8371e5e42709b0a6fe8dd2705315ed367fa848e0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 15:35:56 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 Flags
File: backtrace none

Description Steve 2010-12-16 17:00:32 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: hardinfo
component: hardinfo
crash_function: lup_solve
executable: /usr/bin/hardinfo
kernel: 2.6.35.9-64.fc14.x86_64
package: hardinfo-0.5.1-2.fc12
rating: 4
reason: Process /usr/bin/hardinfo was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1292517936
uid: 500

How to reproduce
-----
1. Open Hardinfo
2. Run FPU FFT
3. Crash
Comment 1 Steve 2010-12-16 17:00:35 UTC 
Created attachment 469175 [details]
File: backtrace
Comment 2 Steve 2011-01-01 15:44:16 UTC 
Package: hardinfo-0.5.1-2.fc12
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Open Hardinfo
2. Run FPU FFT test
3. Crash
Comment 3 abrt-bot 2012-03-20 15:35:56 UTC 
Backtrace analysis found this bug to be similar to bug #569759, closing as duplicate.

Bugs which were found to be similar to this bug: bug #542858, bug #569759, bug #592906, bug #606802, bug #609768, bug #644383, bug #705945, bug #767418

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 569759 ***