Bug 705945

Summary: [abrt] hardinfo-0.5.1-2.fc12: lup_solve: Process /usr/bin/hardinfo was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: dobs <webmaster>
Component: hardinfoAssignee: Adel Gadllah <adel.gadllah>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: adel.gadllah
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6aeb27924ec99ec9d6ec8a5b4eb17ce7eeb5cd11
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 15:35:47 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 dobs 2011-05-18 23:19:03 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 30863 bytes
cmdline: hardinfo
component: hardinfo
Attached file: coredump, 27136000 bytes
crash_function: lup_solve
executable: /usr/bin/hardinfo
kernel: 2.6.35.13-91.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: 1305760635
uid: 500

How to reproduce
-----
1. Information ->Net. updater
2. Sync.
Comment 1 dobs 2011-05-18 23:19:06 UTC 
Created attachment 499718 [details]
File: backtrace
Comment 2 Muhammet Kara 2011-06-11 10:49:57 UTC 
Package: hardinfo-0.5.1-3.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


Comment
-----
Program terminates whenever I click "FPU FFT" benchmark option.
Comment 3 abrt-bot 2012-03-20 15:35:47 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 #663728, bug #767418

This comment is automatically generated.

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