Bug 544568

Summary: [abrt] crash detected in nautilus-2.28.2-1.fc12
Product: [Fedora] Fedora Reporter: Steve <bugzilla>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: mclasen, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:8395756f512a622136bc963226835bae509e8745
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-14 00:55:18 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 Steve 2009-12-05 12:59:47 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Delete some files
2.
3.

Attached file: backtrace
cmdline: nautilus
component: nautilus
executable: /usr/bin/nautilus
kernel: 2.6.31.6-145.fc12.i686.PAE
package: nautilus-2.28.2-1.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Steve 2009-12-05 12:59:50 UTC
Created attachment 376312 [details]
File: backtrace

Comment 2 Tomáš Bžatek 2009-12-08 13:20:24 UTC
I'm really interested in this crash, can you please describe how you managed
Nautilus to crash? This release includes a fix triggering the same issue, but
is obviously not complete. 

Do you use spatial or browser mode? Icon view, list view or compact mode?

Comment 3 Steve 2009-12-08 14:38:58 UTC
I use always; browser mode and list view.

Comment 4 Tomáš Bžatek 2009-12-08 15:59:06 UTC
OK, can you please write detailed repro steps, leading to crash? I need a way to reproduce it here in order to fix that. I.e. sum up any key press, any mouse click, any operation running in background, etc.

Comment 5 Steve 2009-12-08 18:46:09 UTC
I can not reproduce this scenario. I have really no idea. Maybe if it happens again..

Comment 6 Matthias Clasen 2009-12-14 00:55:18 UTC

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