Bug 598518 - [abrt] crash in gvfs-1.6.1-1.fc13: raise: Process /usr/libexec/gvfsd-sftp was killed by signal 6 (SIGABRT)
[abrt] crash in gvfs-1.6.1-1.fc13: raise: Process /usr/libexec/gvfsd-sftp was...
Status: CLOSED DUPLICATE of bug 626875
Product: Fedora
Classification: Fedora
Component: gvfs (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
abrt_hash:f10d00075cd487c7b6c31178dc1...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-01 10:46 EDT by Claudio Rodrigo Pereyra DIaz
Modified: 2015-03-03 17:49 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 10:08:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (11.99 KB, text/plain)
2010-06-01 10:47 EDT, Claudio Rodrigo Pereyra DIaz
no flags Details

  None (edit)
Description Claudio Rodrigo Pereyra DIaz 2010-06-01 10:46:57 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-sftp --spawner :1.7 /org/gtk/gvfs/exec_spaw/12
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-sftp
global_uuid: f10d00075cd487c7b6c31178dc1680f9a31efd1e
kernel: 2.6.33.3-85.fc13.x86_64
package: gvfs-1.6.1-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-sftp was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Claudio Rodrigo Pereyra DIaz 2010-06-01 10:47:04 EDT
Created attachment 418669 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 10:08:45 EST

*** This bug has been marked as a duplicate of bug 626875 ***
Comment 3 Karel Klíč 2010-11-09 10:08:45 EST
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 #626875.

Sorry for the inconvenience.

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