Bug 673738 - [abrt] nautilus-2.32.2.1-1.fc14: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Summary: [abrt] nautilus-2.32.2.1-1.fc14: Process /usr/bin/nautilus was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 693837
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c38440f16cc795424ce7a439356...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-30 09:56 UTC by Michael Bar-Sinai
Modified: 2015-03-03 22:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 17:25:36 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (31.01 KB, text/plain)
2011-01-30 09:56 UTC, Michael Bar-Sinai 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Michael Bar-Sinai 2011-01-30 09:56:15 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: nautilus_window_report_load_underway
executable: /usr/bin/nautilus
kernel: 2.6.35.10-74.fc14.i686
package: nautilus-2.32.2.1-1.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1296377831
uid: 500

How to reproduce
-----
1.Viewed a folder with lots of images (over a network)
2.pressed F3 to get the extra pane
3.had a long wait
4.crash
Comment 1 Michael Bar-Sinai 2011-01-30 09:56:22 UTC 
Created attachment 475996 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 17:25:36 UTC 
Backtrace analysis found this bug to be similar to bug #693837, closing as duplicate.

Bugs which were found to be similar to this bug: bug #622215, bug #627056, bug #657957, bug #659245, bug #667004, bug #693837

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 693837 ***
Note You need to log in before you can comment on or make changes to this bug.