Bug 563107 - [abrt] crash in gvfs-1.4.3-4.fc12
[abrt] crash in gvfs-1.4.3-4.fc12
Product: Fedora
Classification: Fedora
Component: gvfs (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
: 568115 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2010-02-09 04:00 EST by David Harmanec
Modified: 2015-03-03 17:44 EST (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 18:04:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (6.79 KB, text/plain)
2010-02-09 04:00 EST, David Harmanec
no flags Details
second backtrace (5.95 KB, text/plain)
2010-02-10 17:40 EST, David Harmanec
no flags Details

  None (edit)
Description David Harmanec 2010-02-09 04:00:19 EST
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-sftp --spawner :1.1 /org/gtk/gvfs/exec_spaw/2
component: gvfs
executable: /usr/libexec/gvfsd-sftp
package: gvfs-1.4.3-4.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)
Comment 1 David Harmanec 2010-02-09 04:00:23 EST
Created attachment 389697 [details]
File: backtrace
Comment 2 Tomáš Bžatek 2010-02-10 05:04:17 EST
Can you please specify when this crash has happened?
Comment 3 David Harmanec 2010-02-10 17:36:15 EST
Yes, today it happened when I unmounted sftp "mount point" from another computer.
Comment 4 David Harmanec 2010-02-10 17:40:52 EST
Created attachment 390132 [details]
second backtrace
Comment 5 David Harmanec 2010-02-10 17:47:29 EST
I used Tux commander for connecting but I used right-click -> unmount for removal. The crash seems to be reproducible this way.
Comment 6 Tomáš Bžatek 2010-02-11 06:32:02 EST
(In reply to comment #5)
> I used Tux commander for connecting but I used right-click -> unmount for
> removal. The crash seems to be reproducible this way.
Yes, it's a shared GIO mount, no matter how it was mounted.

It's basically a duplicate of bug 557548 (which I'm working on) but the backtrace is slightly different, leaving this open for the moment.
Comment 7 Karel Klíč 2010-05-25 06:23:06 EDT
*** Bug 568115 has been marked as a duplicate of this bug. ***
Comment 8 Bug Zapper 2010-11-03 18:37:15 EDT
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: 
Comment 9 David Harmanec 2010-11-04 14:50:24 EDT
Currently, I am running Fedora 13 (and planning to upgrade to Fedora 14). I haven't experienced this issue for some time, so it's fine with me to close this bug.
Comment 10 Bug Zapper 2010-12-03 18:04:54 EST
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.

Note You need to log in before you can comment on or make changes to this bug.