Bug 680671 - [abrt] nautilus-2.32.2.1-2.fc14: *INT_cairo_paint: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.2.1-2.fc14: *INT_cairo_paint: Process /usr/bin/nautilus ...
Keywords:
Status: CLOSED DUPLICATE of bug 680606
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fbe17fac0ad1fc8cded4b750509...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-26 20:54 UTC by Bernie Innocenti
Modified: 2015-03-03 22:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:49:50 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (26.85 KB, text/plain)
2011-02-26 20:54 UTC, Bernie Innocenti 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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