Bug 649829 - [abrt] gvfs-1.6.4-2.fc14: g_assertion_message: Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 6 (SIGABRT)
Summary: [abrt] gvfs-1.6.4-2.fc14: g_assertion_message: Process /usr/libexec/gvfs-gdu-...
Keywords:
Status: CLOSED DUPLICATE of bug 625919
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:d49dcddfdd70a178a4c2a03af28...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-04 16:08 UTC by ajax
Modified: 2015-03-03 22:54 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 16:40:01 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (5.93 KB, text/plain)
2010-11-04 16:08 UTC, ajax 		no flags Details
View All

Description ajax 2010-11-04 16:08:38 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfs-gdu-volume-monitor
comment: This error occured in fedora 13 as well, it informs me that gvfs has crashed 
component: gvfs
crash_function: g_assertion_message
executable: /usr/libexec/gvfs-gdu-volume-monitor
kernel: 2.6.35.6-45.fc14.i686
package: gvfs-1.6.4-2.fc14
rating: 4
reason: Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1288818454
uid: 500

How to reproduce
-----
1.right after I installed fedora 14
2.right after I login to my user
3.
Comment 1 ajax 2010-11-04 16:08:40 UTC 
Created attachment 457849 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:40:01 UTC 

*** This bug has been marked as a duplicate of bug 625919 ***
Comment 3 Karel Klíč 2010-11-09 16:40:01 UTC 
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 #625919.

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