Bug 605989 - [abrt] crash in nautilus-2.30.1-3.fc13: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in nautilus-2.30.1-3.fc13: Process /usr/bin/nautilus was killed ...
Status: CLOSED DUPLICATE of bug 626207
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:9c99db75bb02f1356060a3d17a8...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-19 20:15 UTC by yyetim
Modified: 2015-03-03 22:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-09 15:31:53 UTC

Attachments (Terms of Use)
File: backtrace (19.98 KB, text/plain)
2010-06-19 20:16 UTC, yyetim
no flags Details

Description yyetim 2010-06-19 20:15:58 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nautilus
comment: Hard to reproduce. Occured once...
component: nautilus
crash_function: nautilus_file_peek_display_name
executable: /usr/bin/nautilus
global_uuid: 9c99db75bb02f1356060a3d17a85f31ed49aa724
package: nautilus-2.30.1-3.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1. Extract this file http://download1.rpmfusion.org/nonfree/fedora/releases/13/Everything/i386/os/kmod-nvidia-
2. It first names the output folder to be something like kmod-nvidia... then renames it to lib. 
3. Before it is renamed to lib, I double-clicked the folder and it gave the exception but couldn't reproduce it again

Comment 1 yyetim 2010-06-19 20:16:00 UTC
Created attachment 425377 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:31:53 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:31:53 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 #626207.

Sorry for the inconvenience.

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