Bug 710540

Summary: [abrt] nautilus-2.32.2.1-2.fc14: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Norm Rossiter <normrossiter>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:a7d17bf895a5938ac4104d868e8e61f5132ad5ae
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 15:34:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Norm Rossiter 2011-06-03 16:29:59 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 17116 bytes
cmdline: nautilus
component: nautilus
Attached file: coredump, 57778176 bytes
crash_function: nautilus_window_slot_info_set_status
executable: /usr/bin/nautilus
kernel: 2.6.35.13-91.fc14.i686
package: nautilus-2.32.2.1-2.fc14
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1307118203
uid: 500

How to reproduce
-----
1.Connected to Windows share.
2.Open file viewer
3.click view extra pane, nothing hapened clicked view unchecked extra pane, clicked view checked extra pane, then nautilus crashed.
Comment 1 Norm Rossiter 2011-06-03 16:30:01 UTC 
Created attachment 502852 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 15:34:02 UTC 
Backtrace analysis found this bug to be similar to bug #652843, closing as duplicate.

Bugs which were found to be similar to this bug: bug #593962, bug #605252, bug #627047, bug #652843, bug #655484, bug #698742, bug #706754

This comment is automatically generated.

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