Bug 689516

Summary: [abrt] nautilus-2.32.2.1-2.fc14: meta_journal_iterate: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Murat OGUZ <muratoguz>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f0306ec641f65a36427555dd1af0265835c92a0c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 16:03:40 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 Murat OGUZ 2011-03-21 17:35:29 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 84299 bytes
cmdline: nautilus
component: nautilus
Attached file: coredump, 102502400 bytes
crash_function: meta_journal_iterate
executable: /usr/bin/nautilus
kernel: 2.6.35.11-83.fc14.x86_64
package: nautilus-2.32.2.1-2.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300728116
uid: 500

How to reproduce
-----
1.is it error?
2.
3.

Comment 1 Murat OGUZ 2011-03-21 17:35:33 UTC
Created attachment 486654 [details]
File: backtrace

Comment 2 Murat OGUZ 2011-03-26 08:12:19 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.is it error
2.
3.

Comment 3 abrt-bot 2012-03-21 16:03:40 UTC
Backtrace analysis found this bug to be similar to bug #663767, closing as duplicate.

Bugs which were found to be similar to this bug: bug #613201, bug #619660, bug #658829, bug #662587, bug #663767, bug #737978

This comment is automatically generated.

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