Bug 666466

Summary: [abrt] nautilus-2.32.2-1.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: medium Docs Contact:
Priority: low    
Version: 14CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c6f0371364d4cadbddda16c6c02890af6c94b313
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 12:50:12 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 Bernie Innocenti 2010-12-31 00:23:46 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: nautilus --sm-client-id 10b731f78573b24116123960603821070600000028900047 --sm-client-state-file /home/bernie/.config/session-state/nautilus-1293073076.state
component: nautilus
crash_function: *INT_cairo_paint
executable: /usr/bin/nautilus
kernel: 2.6.35.10-74.fc14.x86_64
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)
How to reproduce: I'm not sure how the crash happened. Perhaps it was on monitor plug or unplug.
time: 1293754444
uid: 1000
Comment 1 Bernie Innocenti 2010-12-31 00:23:49 UTC 
Created attachment 471230 [details]
File: backtrace
Comment 2 Bernie Innocenti 2011-01-01 17:17:17 UTC 
Package: nautilus-2.32.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Not sure how it happened. It was probably at login time.
Comment 3 abrt-bot 2012-03-30 12:50:12 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 #666829, bug #667084, bug #680606, bug #680671, bug #718702

This comment is automatically generated.

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