Bug 683520 - [abrt] gvfs-1.6.6-1.fc14: on_pending_call_notify: Process /usr/libexec/gvfsd-sftp was killed by signal 6 (SIGABRT)
Summary: [abrt] gvfs-1.6.6-1.fc14: on_pending_call_notify: Process /usr/libexec/gvfsd-...
Keywords:
Status: CLOSED DUPLICATE of bug 689848
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f9be283c9e47887f98581fca775...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 16:10 UTC by Alfredo Pons Menargues
Modified: 2015-03-03 22:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 19:29:20 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (10.71 KB, text/plain)
2011-03-09 16:10 UTC, Alfredo Pons Menargues 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alfredo Pons Menargues 2011-03-09 16:10:21 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 10967 bytes
cmdline: /usr/libexec/gvfsd-sftp --spawner :1.10 /org/gtk/gvfs/exec_spaw/8
component: gvfs
Attached file: coredump, 9117696 bytes
crash_function: on_pending_call_notify
executable: /usr/libexec/gvfsd-sftp
kernel: 2.6.35.11-83.fc14.i686.PAE
package: gvfs-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-sftp was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299686700
uid: 500

How to reproduce
-----
1. 1
2.
3.
Comment 1 Alfredo Pons Menargues 2011-03-09 16:10:24 UTC 
Created attachment 483253 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 19:29:20 UTC 
Backtrace analysis found this bug to be similar to bug #689848, closing as duplicate.

Bugs which were found to be similar to this bug: bug #643262, bug #689848

This comment is automatically generated.

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