Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 607848 - [abrt] crash in gvfs-afc-1.6.2-1.fc13: Process /usr/libexec/gvfsd-afc was killed by signal 11 (SIGSEGV)
[abrt] crash in gvfs-afc-1.6.2-1.fc13: Process /usr/libexec/gvfsd-afc was kil...
Status: CLOSED DUPLICATE of bug 602034
Product: Fedora
Classification: Fedora
Component: gvfs (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-06-24 22:22 EDT by mdmpsyd@gmail.com
Modified: 2015-03-03 17:50 EST (History)
4 users (show)

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

Attachments (Terms of Use)
File: backtrace (38.03 KB, text/plain)
2010-06-24 22:22 EDT, mdmpsyd@gmail.com
no flags Details

  None (edit)
Description mdmpsyd@gmail.com 2010-06-24 22:22:12 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-afc --spawner :1.1 /org/gtk/gvfs/exec_spaw/2
component: gvfs
crash_function: g_vfs_backend_afc_set_info_from_afcinfo
executable: /usr/libexec/gvfsd-afc
global_uuid: 975a6690dab561418a4d6db8d4248bf9d96be0a9
package: gvfs-afc-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-afc was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 mdmpsyd@gmail.com 2010-06-24 22:22:15 EDT
Created attachment 426747 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 08:28:14 EST

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

Sorry for the inconvenience.

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