Bug 638346 - [abrt] gvfs-1.6.2-1.fc13: g_vfs_job_emit_finished: Process /usr/libexec/gvfsd-sftp was killed by signal 11 (SIGSEGV)
Summary: [abrt] gvfs-1.6.2-1.fc13: g_vfs_job_emit_finished: Process /usr/libexec/gvfsd...
Keywords:
Status: CLOSED DUPLICATE of bug 630757
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4a57f27b442e4ccc7b38a2010ba...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-28 19:51 UTC by Benjamin Otte
Modified: 2015-03-03 22:53 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:20:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (7.35 KB, text/plain)
2010-09-28 19:51 UTC, Benjamin Otte 		no flags Details
View All

Description Benjamin Otte 2010-09-28 19:51:33 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-sftp --spawner :1.7 /org/gtk/gvfs/exec_spaw/5
component: gvfs
crash_function: g_vfs_job_emit_finished
executable: /usr/libexec/gvfsd-sftp
kernel: 2.6.34.6-54.fc13.x86_64
package: gvfs-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-sftp was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1285699210
uid: 500

How to reproduce
-----
1. Navigate to SFTP share in Nautilus
2. Double-click a file in Totem
3. be lucky
It only happened the first time I tried to play the file. The second time the file opened fine but Totem complained that it wasn't seekable.
I can get you the file if you care.
Comment 1 Benjamin Otte 2010-09-28 19:51:36 UTC 
Created attachment 450295 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:20:50 UTC 

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

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