Bug 806367

Summary: [abrt] nautilus-2.30.1-6.fc13: ImportTIFF_LocTextASCII: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: James Wood <jasjwoody1958_1>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:4fbf538f6555a1e0f369378b5e96b411db723481
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 15:02:56 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 James Wood 2012-03-23 15:02:22 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: nautilus --sm-client-id 10c2022fbfeffa55131393339928864100000022620033 --sm-client-state-file /home/Jeffery/.config/session-state/nautilus-1332317800.state
component: nautilus
crash_function: ImportTIFF_LocTextASCII
executable: /usr/bin/nautilus
kernel: 2.6.34.9-69.fc13.x86_64
package: nautilus-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1332510713
uid: 500

How to reproduce
-----
1.I was attemting to open a .jpg file using Image Viewer.
2.File didn't open, instead Nautilus crashed.
3.
Comment 1 James Wood 2012-03-23 15:02:26 UTC 
Created attachment 572298 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 15:02:56 UTC 
Backtrace analysis found this bug to be similar to bug #680838, closing as duplicate.

Bugs which were found to be similar to this bug: bug #607833, bug #615716, bug #680838, bug #733169

This comment is automatically generated.

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