Bug 662602

Summary: [abrt] nautilus-2.32.2-1.fc14: directory_count_stop: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: D.S. Ljungmark <spider>
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:3f26f5cfb5ce4e145d8bd1a854546d8dee318c21
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 19:01:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description D.S. Ljungmark 2010-12-13 10:55:19 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: nautilus
comment: I realised I copied the files into the wrong place and moved the target while the copy was still running.  Realised that nautilus/gfile can't handle that and crashed .
component: nautilus
crash_function: directory_count_stop
executable: /usr/bin/nautilus
package: nautilus-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1292237515
uid: 1000

How to reproduce
1. Copy a directory from one disk onto a detachable storage (android phone)
2. While the copy operation runs, move the directory you just copied one level up in the target tree
3. watch as it crashes

Comment 1 D.S. Ljungmark 2010-12-13 10:55:22 UTC
Created attachment 468341 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 19:01:40 UTC
Backtrace analysis found this bug to be similar to bug #727399, closing as duplicate.

Bugs which were found to be similar to this bug: bug #547558, bug #655488, bug #668974, bug #689183, bug #691091, bug #727399, bug #733867

This comment is automatically generated.

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