Bug 584028 - [abrt] crash in nautilus-2.30.0-2.fc13: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in nautilus-2.30.0-2.fc13: Process /usr/bin/nautilus was killed ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f2eca7ca420808aa3d856092521...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-20 14:57 UTC by Pablo Iranzo Gómez
Modified: 2015-03-03 22:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-21 06:27:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (27.82 KB, text/plain)
2010-04-20 14:57 UTC, Pablo Iranzo Gómez 		no flags Details
View All

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