Bug 589987 - [abrt] crash in nautilus-2.28.4-2.fc12: g_hash_table_lookup_node: Process /usr/bin/nautilus was killed by signal 8 (SIGFPE)
Summary: [abrt] crash in nautilus-2.28.4-2.fc12: g_hash_table_lookup_node: Process /us...
Status: CLOSED DUPLICATE of bug 581361
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus   
(Show other bugs)
Version: 12
Hardware: x86_64 Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4e0d65254bac94b0079aed30f7b...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-07 13:06 UTC by aten
Modified: 2015-03-03 22:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 09:24:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (31.21 KB, text/plain)
2010-05-07 13:06 UTC, aten 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description aten 2010-05-07 13:06:28 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nautilus --no-desktop
component: nautilus
crash_function: g_hash_table_lookup_node
executable: /usr/bin/nautilus
global_uuid: 4e0d65254bac94b0079aed30f7b081941082530b
kernel: 2.6.32.11-99.fc12.x86_64
package: nautilus-2.28.4-2.fc12
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 8 (SIGFPE)
release: Fedora release 12 (Constantine)
Comment 1 aten 2010-05-07 13:06:29 UTC 
Created attachment 412348 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:24:49 UTC 

*** This bug has been marked as a duplicate of bug 581361 ***
Comment 3 Karel Klíč 2010-05-25 09:24:49 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #581361.

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