Bug 579361

Summary: [abrt] crash in gvfs-1.4.3-7.fc12: Process /usr/libexec/gvfsd-dav was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: jim wilson <wilsonjallan>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: alexl, bnocera, bugs, carlosgarcia83, jmcc2950, liblit, octerman, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:8363052b87848256290a7066ce402d7967f29e18
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 16:20:53 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 jim wilson 2010-04-04 15:51:46 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-dav --spawner :1.7 /org/gtk/gvfs/exec_spaw/13
component: gvfs
executable: /usr/libexec/gvfsd-dav
kernel: 2.6.32.10-90.fc12.i686.PAE
package: gvfs-1.4.3-7.fc12
rating: 4
reason: Process /usr/libexec/gvfsd-dav was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Attempt to access publicly shared files from localhost
2.
3.

Comment 1 jim wilson 2010-04-04 15:51:49 UTC
Created attachment 404404 [details]
File: backtrace

Comment 2 jmcc2950 2010-04-17 09:50:03 UTC

How to reproduce
-----
1.Firefox open to Fedora
2.Downloading beta Fedora13 install DVD
3.Doing S/W update in F12


Comment
-----
Had web page open in Firefox and was downloading beta Fedora13 install DVD & was doing S/W update in F12

Comment 3 Samuel Hodges 2010-04-19 01:56:00 UTC

Comment
-----
just trying to connect to another f12 machine on my home network. I was playing around with the fire wall settings to allow mDNS services, saw the machine appear in the network folder, click on it and that is it. Also it did not connect and I got an error. one saying somting about blar blar-freedesktop.org something and the other says "http error: can not connect to destination".

Comment 4 Bug Zapper 2010-11-03 17:53:47 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-12-03 16:20:53 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.