Bug 676926

Summary: [abrt] nautilus-2.32.2.1-2.fc14: g_type_check_instance_cast: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: sly <slybloty>
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: i686   
OS: Unspecified   
Whiteboard: abrt_hash:cb893f37f4c6e82a494be66c2ddd43967e7ebedb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:48:36 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 sly 2011-02-11 21:12:41 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus --sm-client-id 10dd7f9d2a997a3ee3128882211074180200000018360035 --sm-client-state-file /home/sly/.config/session-state/nautilus-1293298319.state
component: nautilus
crash_function: g_type_check_instance_cast
executable: /usr/bin/nautilus
kernel: 2.6.35.9-64.fc14.i686
package: nautilus-2.32.2.1-2.fc14
rating: 3
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Clicked the arrow down to open the back history and it crashed.
time: 1297458602
uid: 500
Comment 1 sly 2011-02-11 21:12:43 UTC 
Created attachment 478312 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 14:48:36 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 #682476, bug #737465

This comment is automatically generated.

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