Bug 680671

Summary: [abrt] nautilus-2.32.2.1-2.fc14: *INT_cairo_paint: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bernie Innocenti <bernie+fedora>
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: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fbe17fac0ad1fc8cded4b7505099f3a2f24d5dc1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 12:49:50 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 Bernie Innocenti 2011-02-26 20:54:43 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 27493 bytes
cmdline: nautilus --sm-client-id 10b731f78573b24116123960603821070600000028900047 --sm-client-state-file /home/bernie/.config/session-state/nautilus-1295657036.state
component: nautilus
Attached file: coredump, 60633088 bytes
crash_function: *INT_cairo_paint
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)
How to reproduce: 1. I believe I wasn't interacting with Nautilus at all at the time of the crash, but I can't be sure about it.
time: 1298734187
uid: 1000
Comment 1 Bernie Innocenti 2011-02-26 20:54:45 UTC 
Created attachment 481191 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 12:49:50 UTC 
Backtrace analysis found this bug to be similar to bug #680606, closing as duplicate.

Bugs which were found to be similar to this bug: bug #650032, bug #652148, bug #657120, bug #666466, bug #666829, bug #667084, bug #680606, bug #718702

This comment is automatically generated.

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