Bug 555598

Summary: [abrt] crash in gvfs-1.4.3-2.fc12
Product: [Fedora] Fedora Reporter: Bill Case <billlinux>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: alexl, bnocera, claudiorodrigo, gabriel, gorbyo, jerlyon, joflixo, marbolangos, mat.booth, musmeh55, otto_rey, tbzatek, tomas.vanderka, tsmetana, watzkej, xurzwi2q1
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:840011b2f4df59543b78cf135454d1a158cc23dd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-05 17:16:17 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 Bill Case 2010-01-14 21:42:45 UTC 
abrt 1.0.3 detected a crash.

How to reproduce
-----
1.In 'Places => sftp gerald (i.e. remote computer on home two machine LAN)
2.right click => pop up=> unmount
3.

Comment
-----
I believe this bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=554236
which I have been working to fix.  Lots of the details of what proceeded are with bug #554236.

Attached file: backtrace
cmdline: /usr/libexec/gvfsd-sftp --spawner :1.4 /org/gtk/gvfs/exec_spaw/10
component: gvfs
executable: /usr/libexec/gvfsd-sftp
kernel: 2.6.31.9-174.fc12.x86_64
package: gvfs-1.4.3-2.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 Bill Case 2010-01-14 21:42:47 UTC 
Created attachment 384465 [details]
File: backtrace
Comment 2 Mat Booth 2010-01-16 14:01:23 UTC 
I encountered this bug umounting my Fedora People webspace that I connect to using Gnome's Places->Connect to Server dialog box.
Comment 3 Tomáš Bžatek 2010-02-05 17:16:17 UTC 

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