Bug 544568 - [abrt] crash detected in nautilus-2.28.2-1.fc12
Summary: [abrt] crash detected in nautilus-2.28.2-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 541709
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8395756f512a622136bc9632268...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-05 12:59 UTC by Steve
Modified: 2015-03-03 22:42 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-14 00:55:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (16.35 KB, text/plain)
2009-12-05 12:59 UTC, Steve 		no flags Details
View All

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