Bug 675367

Summary: [abrt] nautilus-2.32.2.1-2.fc14: rename_callback: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Pichan <pichan19>
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, drindt, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5e320e4900f0d664c0396ee5e7cd85250243e424
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 14:50:03 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 Pichan 2011-02-05 07:41:28 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: rename_callback
executable: /usr/bin/nautilus
kernel: 2.6.35.10-74.fc14.x86_64
package: nautilus-2.32.2.1-2.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: Renaming 1,5 GB mkv
time: 1296891662
uid: 501

Comment 1 Pichan 2011-02-05 07:41:31 UTC
Created attachment 477168 [details]
File: backtrace

Comment 2 Daniel Rindt 2011-03-06 12:47:02 UTC
Package: nautilus-2.32.2.1-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. create folder on smb share
2. try renaming it -> the "in progress dialog appears"
3. crash


Comment
-----
tried to create a new folder and later i would rename it

Comment 3 abrt-bot 2012-03-30 14:50:03 UTC
Backtrace analysis found this bug to be similar to bug #739527, closing as duplicate.

Bugs which were found to be similar to this bug: bug #556444, bug #579295, bug #588301, bug #590338, bug #611269, bug #617700, bug #626643, bug #628313, bug #646028, bug #651423, bug #658865, bug #676220, bug #739527

This comment is automatically generated.

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