Bug 619389 - [abrt] crash in nautilus-2.30.1-4.fc13: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in nautilus-2.30.1-4.fc13: Process /usr/bin/nautilus was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 626207
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:c7c7d955e73463b5c544a3b47a3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-29 12:59 UTC by Davide Repetto
Modified: 2015-03-03 22:51 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:32:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (36.61 KB, text/plain)
2010-07-29 12:59 UTC, Davide Repetto 		no flags Details
View All

Description Davide Repetto 2010-07-29 12:59:06 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: nautilus_file_peek_display_name
executable: /usr/bin/nautilus
global_uuid: c7c7d955e73463b5c544a3b47a3e0f8a88f60ed8
kernel: 2.6.33.6-147.fc13.i686.PAE
package: nautilus-2.30.1-4.fc13
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: I was not able to reproduce.

comment
-----
The crash happened while I was moving some files to trash on an smb share mounted as:
//smb/swap/ on /net/swap type cifs (rw,mand)
with unix extensions disabled
Comment 1 Davide Repetto 2010-07-29 12:59:13 UTC 
Created attachment 435269 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:32:56 UTC 

*** This bug has been marked as a duplicate of bug 626207 ***
Comment 3 Karel Klíč 2010-11-09 15:32:56 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.