Bug 654496 - [abrt] gvfs-archive-1.6.6-1.fc14: g_assertion_message: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
Summary: [abrt] gvfs-archive-1.6.6-1.fc14: g_assertion_message: Process /usr/libexec/g...
Keywords:
Status: CLOSED DUPLICATE of bug 649388
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fc202dbe6172e97289ac6e8310a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-18 00:45 UTC by cao
Modified: 2015-03-03 22:55 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:04:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (6.69 KB, text/plain)
2010-11-18 00:45 UTC, cao 		no flags Details
View All

Description cao 2010-11-18 00:45:45 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-archive --spawner :1.13 /org/gtk/gvfs/exec_spaw/2
component: gvfs
crash_function: g_assertion_message
executable: /usr/libexec/gvfsd-archive
kernel: 2.6.35.6-48.fc14.i686
package: gvfs-archive-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-archive was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1290040723
uid: 500
Comment 1 cao 2010-11-18 00:45:48 UTC 
Created attachment 461188 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 12:04:24 UTC 
Backtrace analysis found this bug to be similar to bug #649388, closing as duplicate.

Bugs which were found to be similar to this bug: bug #560325, bug #562420, bug #568398, bug #570390, bug #575305, bug #579109, bug #583144, bug #585578, bug #591453, bug #592634, bug #605880, bug #609794, bug #613728, bug #628148, bug #647207, bug #649388, bug #653649, bug #657424, bug #670469, bug #680600, bug #694187

This comment is automatically generated.

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