Bug 584028

Summary: [abrt] crash in nautilus-2.30.0-2.fc13: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Pablo Iranzo Gómez <pablo.iranzo>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:f2eca7ca420808aa3d8560925214bf206493ece8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-21 06:27:24 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 Pablo Iranzo Gómez 2010-04-20 14:57:09 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nautilus
component: nautilus
executable: /usr/bin/nautilus
global_uuid: f2eca7ca420808aa3d8560925214bf206493ece8
kernel: 2.6.33.2-41.fc13.x86_64
package: nautilus-2.30.0-2.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.'Move' one file from local fs to remote fs over gvfs-smb
2.File starts copying
3. At the end of the copy, nautilus crashes, but file was moved ok (if copying, it doesn't crash)
Comment 1 Pablo Iranzo Gómez 2010-04-20 14:57:12 UTC 
Created attachment 407834 [details]
File: backtrace
Comment 2 Tomáš Bžatek 2010-04-20 15:03:03 UTC 
This is a crash in unsupported 3rd party dropbox extension, try disabling it first.
Comment 3 Pablo Iranzo Gómez 2010-04-20 15:18:28 UTC 
Ok, will have it on hold until I get another file with a similar size to the one I copied.

Thanks!
Comment 4 Pablo Iranzo Gómez 2010-04-21 06:27:24 UTC 
Couldn't reproduce it without the extension, closing this bug