Bug 663728 - [abrt] hardinfo-0.5.1-2.fc12: lup_solve: Process /usr/bin/hardinfo was killed by signal 11 (SIGSEGV)
Summary: [abrt] hardinfo-0.5.1-2.fc12: lup_solve: Process /usr/bin/hardinfo was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 569759
Alias: None
Product: Fedora
Classification: Fedora
Component: hardinfo
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8371e5e42709b0a6fe8dd270531...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-16 17:00 UTC by Steve
Modified: 2012-03-20 15:35 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:35:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (26.68 KB, text/plain)
2010-12-16 17:00 UTC, Steve
no flags Details

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 ***


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