Bug 664112

Summary: [abrt] nautilus-2.32.2-1.fc14: g_type_check_instance_cast: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Andrew Kornak <akornak>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: bugs.michael, ccecchi, katalystk, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:0cf241d5de3c48e81fc62afe8f31abd90f5a44cb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-21 10:21:27 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 Andrew Kornak 2010-12-18 10:06:16 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus
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.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1292666520
uid: 500

How to reproduce
-----
1. Viewing jpeg image
2. nautilus crash
3.

Comment 1 Andrew Kornak 2010-12-18 10:06:19 UTC
Created attachment 469499 [details]
File: backtrace

Comment 2 Katalyst 2010-12-23 18:29:22 UTC
Package: nautilus-2.32.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Right clicked on a folder
2.
3.

Comment 3 Andrew Kornak 2011-01-04 17:06:26 UTC
Package: nautilus-2.32.2-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. ran DVDRipomatic with qt3
2. crash
3.

Comment 4 Michael Schwendt 2011-02-21 10:21:27 UTC

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