Bug 680769

Summary: [abrt] nautilus-2.32.2.1-2.fc14: nautilus_path_bar_scroll_down: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: moromario
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, darmas, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:ba95bc84c5b226a9b8883a72a5b8f40b4a8ab9e9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:57: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 moromario 2011-02-27 16:41:46 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 29051 bytes
cmdline: nautilus
comment: try using a non maximized nautilus window and scroll the upper path bar to copy files
component: nautilus
Attached file: coredump, 73035776 bytes
crash_function: nautilus_path_bar_scroll_down
executable: /usr/bin/nautilus
kernel: 2.6.35.11-83.fc14.i686
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)
time: 1298820943
uid: 500

How to reproduce
-----
1. Open Nautilus 
2. Start copying files from a folder to another using the path bar
3. At a certain moment nautilus crashed
Comment 1 moromario 2011-02-27 16:41:50 UTC 
Created attachment 481257 [details]
File: backtrace
Comment 2 Darmas 2011-03-30 03:00:32 UTC 
Package: nautilus-2.32.2.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
I was locked out of my room
Comment 3 abrt-bot 2012-03-21 14:57:12 UTC 
Backtrace analysis found this bug to be similar to bug #702188, closing as duplicate.

Bugs which were found to be similar to this bug: bug #650493, bug #655284, bug #699096, bug #702188, bug #704810

This comment is automatically generated.

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