Bug 591927 - [abrt] crash in nautilus-2.30.1-3.fc13: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in nautilus-2.30.1-3.fc13: raise: Process /usr/bin/nautilus was ...
Keywords:
Status: CLOSED DUPLICATE of bug 591740
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:868fb49d2af8bc47f08b1c8161a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 13:52 UTC by Markku Korkeala
Modified: 2015-03-03 22:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 17:30:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (59.55 KB, text/plain)
2010-05-13 13:52 UTC, Markku Korkeala 		no flags Details
View All

Description Markku Korkeala 2010-05-13 13:52:17 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nautilus
comment: I tried to copy big chunk of files (over 50000, almost 30 GB) from USB HDD to my computer and nautilus crashed almost at the end of the file transfer.
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
global_uuid: 868fb49d2af8bc47f08b1c8161a81ae3e0c36852
kernel: 2.6.33.3-85.fc13.i686
package: nautilus-2.30.1-3.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. 
2.
3.
Comment 1 Markku Korkeala 2010-05-13 13:52:19 UTC 
Created attachment 413766 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 17:30:55 UTC 

*** This bug has been marked as a duplicate of bug 591740 ***
Comment 3 Karel Klíč 2010-11-08 17:30:55 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #591740.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.