Bug 682476

Summary: [abrt] nautilus-2.32.2.1-2.fc14: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bill Bauman <bbauman>
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, gdrapeau, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:53830e075023798a174d32d2d2dd892470022152
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:48:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Bill Bauman 2011-03-05 21:46:24 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 32454 bytes
cmdline: nautilus
component: nautilus
Attached file: coredump, 65478656 bytes
crash_function: nautilus_bookmark_menu_item_new
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: 1299360189
uid: 500

How to reproduce
-----
1. Unsure, exactly
2. Attempted to Cut/Paste files from Trash to a new directory
3.
Comment 1 Bill Bauman 2011-03-05 21:46:26 UTC 
Created attachment 482474 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 14:48:25 UTC 
Backtrace analysis found this bug to be similar to bug #737465, closing as duplicate.

Bugs which were found to be similar to this bug: bug #541700, bug #543306, bug #561292, bug #561604, bug #567284, bug #567451, bug #587945, bug #638947, bug #639503, bug #643025, bug #673611, bug #676926, bug #737465

This comment is automatically generated.

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