Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
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
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:4e0d65254bac94b0079aed30f7b...
Depends On:
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:
Clone Of:
Last Closed: 2010-05-25 09:24:49 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-07 13:06 UTC, aten
no flags Details

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