Bug 664112 - [abrt] nautilus-2.32.2-1.fc14: g_type_check_instance_cast: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.2-1.fc14: g_type_check_instance_cast: Process /usr/bin/n...
Keywords:
Status: CLOSED DUPLICATE of bug 655733
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0cf241d5de3c48e81fc62afe8f3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-18 10:06 UTC by Andrew Kornak
Modified: 2015-03-03 22:56 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-21 10:21:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (35.88 KB, text/plain)
2010-12-18 10:06 UTC, Andrew Kornak 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.