Bug 648293 - [abrt] nautilus-2.32.0-1.fc14: nautilus_file_clear_info: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.32.0-1.fc14: nautilus_file_clear_info: Process /usr/bin/nau...
Keywords:
Status: CLOSED DUPLICATE of bug 671504
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:50966cee9d45c5a69586d106c9e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-31 21:43 UTC by Felix Möller
Modified: 2015-03-03 22:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:41:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (25.80 KB, text/plain)
2010-10-31 21:43 UTC, Felix Möller
no flags Details

Description Felix Möller 2010-10-31 21:43:49 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: nautilus_file_clear_info
executable: /usr/bin/nautilus
kernel: 2.6.35.6-48.fc14.i686.PAE
package: nautilus-2.32.0-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288555392
uid: 500

How to reproduce
-----
I created a .htaccess file on a ftp mounted folder in nautilus.

I cannot reproduce it yet...

Comment 1 Felix Möller 2010-10-31 21:43:52 UTC
Created attachment 456756 [details]
File: backtrace

Comment 2 Felix Möller 2010-10-31 21:50:30 UTC
The source for the backtrace is at:
http://git.gnome.org/browse/nautilus/tree/libnautilus-private/nautilus-file.c#n420

Comment 3 abrt-bot 2012-03-20 16:41:15 UTC
Backtrace analysis found this bug to be similar to bug #671504, closing as duplicate.

Bugs which were found to be similar to this bug: bug #580340, bug #671504

This comment is automatically generated.

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


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