Bug 557577 - [abrt] crash in gvfs-1.4.3-3.fc12
Summary: [abrt] crash in gvfs-1.4.3-3.fc12
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:03717883b104dd7f0aba25f0967...
: 552790 556935 566929 568976 585556 588534 590003 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-01-21 20:56 UTC by Paul W. Frields
Modified: 2015-03-03 22:44 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-04 00:01:28 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (4.68 KB, text/plain)
2010-01-21 20:56 UTC, Paul W. Frields
no flags Details

Description Paul W. Frields 2010-01-21 20:56:16 UTC
abrt 1.0.3 detected a crash.

How to reproduce
Not sure if I can reproduce this. I was able to successfully ping the sftp-connected system right after Rhythmbox quit.

If it matters at all, I am using Rhythmbox over a VNC session.  My path looks like this: I'm on the console of machine4, VNC'd to machine11, and machine11 was running Rhythmbox playing through the PulseAudio server on machine4, and using files from an SFTP connection to machine2.

Comment: Segfault when playing files on Rhythmbox from gvfs-sftp mount
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-sftp --spawner :1.8 /org/gtk/gvfs/exec_spaw/12
component: gvfs
executable: /usr/libexec/gvfsd-sftp
package: gvfs-1.4.3-3.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Paul W. Frields 2010-01-21 20:56:18 UTC
Created attachment 386008 [details]
File: backtrace

Comment 2 Paul W. Frields 2010-01-21 20:58:41 UTC
I should have also noted that all three machines are F12 x86_64.  The file share on machine2 is an external USB hard disk.  The log on machine2 shows no anomalies at the time of the segfault on machine11.

Comment 3 Tomáš Bžatek 2010-02-05 17:10:58 UTC
Could this happen when you unmounted an active sftp mount? I.e. bug 557548?

Comment 4 Paul W. Frields 2010-02-08 17:18:54 UTC
Well, I didn't manually unmount anything at the times these problems have happened.  It's possible the mount failed in some way that wasn't apparent to me.

Comment 5 Karel Klíč 2010-02-24 17:06:04 UTC
*** Bug 552790 has been marked as a duplicate of this bug. ***

Comment 6 Karel Klíč 2010-02-24 17:06:09 UTC
*** Bug 556935 has been marked as a duplicate of this bug. ***

Comment 7 Karel Klíč 2010-02-24 17:06:14 UTC
*** Bug 566929 has been marked as a duplicate of this bug. ***

Comment 8 Karel Klíč 2010-05-25 10:03:47 UTC
*** Bug 568976 has been marked as a duplicate of this bug. ***

Comment 9 Karel Klíč 2010-05-25 10:03:51 UTC
*** Bug 585556 has been marked as a duplicate of this bug. ***

Comment 10 Karel Klíč 2010-05-25 10:03:55 UTC
*** Bug 588534 has been marked as a duplicate of this bug. ***

Comment 11 Karel Klíč 2010-05-25 10:04:00 UTC
*** Bug 590003 has been marked as a duplicate of this bug. ***

Comment 12 Bug Zapper 2010-11-04 00:17:51 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: 

Comment 13 Bug Zapper 2010-12-04 00:01:28 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.

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