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 613202 - [abrt] crash in gvfs-1.6.2-1.fc13: apply_journal_to_builder: Process /usr/libexec/gvfsd-metadata was killed by signal 11 (SIGSEGV)
[abrt] crash in gvfs-1.6.2-1.fc13: apply_journal_to_builder: Process /usr/lib...
Status: CLOSED DUPLICATE of bug 608748
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-07-09 20:51 EDT by Dmitry Petrich
Modified: 2015-03-03 17:50 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 10:38:33 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 (13.34 KB, text/plain)
2010-07-09 20:51 EDT, Dmitry Petrich
no flags Details

  None (edit)
Description Dmitry Petrich 2010-07-09 20:51:51 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-metadata
component: gvfs
crash_function: apply_journal_to_builder
executable: /usr/libexec/gvfsd-metadata
global_uuid: ea9e7335e7122d4d3369f984cfc18785cd7aa4d8
package: gvfs-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-metadata was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Dmitry Petrich 2010-07-09 20:51:56 EDT
Created attachment 430782 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 10:38:33 EST

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

Sorry for the inconvenience.

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