Bug 672087 - [abrt] gvfs-1.6.6-1.fc14: gkr_operation_block_and_unref: Process /usr/libexec/gvfsd-ftp was killed by signal 6 (SIGABRT)
Summary: [abrt] gvfs-1.6.6-1.fc14: gkr_operation_block_and_unref: Process /usr/libexec...
Keywords:
Status: CLOSED DUPLICATE of bug 699807
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3d061ab32e1b37deaa8a19c63e7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-23 21:31 UTC by dobs
Modified: 2015-03-03 22:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:03:16 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (10.10 KB, text/plain)
2011-01-23 21:31 UTC, dobs 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description dobs 2011-01-23 21:31:56 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-ftp --spawner :1.10 /org/gtk/gvfs/exec_spaw/8
component: gvfs
crash_function: gkr_operation_block_and_unref
executable: /usr/libexec/gvfsd-ftp
kernel: 2.6.35.10-74.fc14.x86_64
package: gvfs-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-ftp was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Try to FTP connect
time: 1295818272
uid: 500
Comment 1 dobs 2011-01-23 21:31:59 UTC 
Created attachment 474859 [details]
File: backtrace
Comment 2 Jan Teichmann 2011-04-07 13:03:56 UTC 
Package: gvfs-1.6.6-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
I did try to mount a ftp source
Comment 3 abrt-bot 2012-03-30 12:03:16 UTC 
Backtrace analysis found this bug to be similar to bug #699807, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 699807 ***
Note You need to log in before you can comment on or make changes to this bug.