Bug 614912

Summary: [abrt] crash in nautilus-2.30.1-3.fc13: raise: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Andre Costa <andre.ocosta>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE 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:26f54e74ca6fd735a22aa18f979610f0380cb7d0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 17:27:13 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 Andre Costa 2010-07-15 14:41:12 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nautilus
comment: I had one nautilus window opened with a remote (sftp://) filesystem, and I dragged files from a local directory to a remote dir (these files would override files on the remote dir). After the crash I tried the same operation again and it worked just fine, so it's not a deterministic failure.
component: nautilus
crash_function: raise
executable: /usr/bin/nautilus
global_uuid: 26f54e74ca6fd735a22aa18f979610f0380cb7d0
kernel: 2.6.33.6-147.fc13.x86_64
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)

Comment 1 Andre Costa 2010-07-15 14:41:16 UTC
Created attachment 432103 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 17:27:13 UTC

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

Comment 3 Karel Klíč 2010-11-08 17:27:13 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 #633273.

Sorry for the inconvenience.