Bug 619486

Summary: [abrt] crash in nautilus-2.30.1-4.fc13: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Steve Dowe <sd>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:0616c2ab50021b310906eebb6512bd0bb316e889
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 13:56:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Steve Dowe 2010-07-29 16:32:07 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nautilus --sm-client-id 10bd08d192aa3b9674127554684437407000000024230027 --sm-client-state-file /home/steve/.config/session-state/nautilus-1280360807.state
comment: As described in steps to reproduce
component: nautilus
crash_function: nautilus_bookmark_menu_item_new
executable: /usr/bin/nautilus
global_uuid: 0616c2ab50021b310906eebb6512bd0bb316e889
kernel: 2.6.33.6-147.fc13.x86_64
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
-----
1. Browse a directory on NFS share (mounted via AutoFS), navigate using forward/backward buttons in Nautilus
2. Right click a directory for Properties, get directory size count, close window then hit forward > once
3. Then clicked on < Back down-arrow to view history
Comment 1 Steve Dowe 2010-07-29 16:32:10 UTC 
Created attachment 435343 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:56:47 UTC 

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

Sorry for the inconvenience.