Bug 601928 - [abrt] crash in gvfs-archive-1.4.3-6.el6: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
[abrt] crash in gvfs-archive-1.4.3-6.el6: Process /usr/libexec/gvfsd-archive ...
Status: CLOSED DUPLICATE of bug 596716
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gvfs (Show other bugs)
x86_64 Linux
low Severity medium
: rc
: ---
Assigned To: Tomáš Bžatek
Depends On:
  Show dependency treegraph
Reported: 2010-06-08 17:20 EDT by uzoma nwosu
Modified: 2015-03-03 17:49 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-21 13:59:47 EDT
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 (16.51 KB, text/plain)
2010-06-08 17:20 EDT, uzoma nwosu
no flags Details

  None (edit)
Description uzoma nwosu 2010-06-08 17:20:43 EDT
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-archive file=/media/PG110GB/rhelbackup.tar.bz2
comment: don't know.  I came back to the laptop and the ABRT light was on.
component: gvfs
executable: /usr/libexec/gvfsd-archive
kernel: 2.6.32-19.el6.x86_64
package: gvfs-archive-1.4.3-6.el6
rating: 4
reason: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
Comment 1 uzoma nwosu 2010-06-08 17:20:45 EDT
Created attachment 422365 [details]
File: backtrace
Comment 3 RHEL Product and Program Management 2010-06-08 17:33:18 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 4 Matthias Clasen 2010-06-21 13:59:47 EDT

*** This bug has been marked as a duplicate of bug 596716 ***

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