Bug 624124 - [abrt] crash in gvfs-afc-1.6.2-1.fc13: command_read_cb: Process /usr/libexec/gvfsd-afc was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gvfs-afc-1.6.2-1.fc13: command_read_cb: Process /usr/libexec/...
Keywords:
Status: CLOSED DUPLICATE of bug 628501
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1de2db8fa73d1f4217b9953249a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-13 18:19 UTC by Saikat Guha
Modified: 2015-03-03 22:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:21:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (14.56 KB, text/plain)
2010-08-13 18:19 UTC, Saikat Guha 		no flags Details
View All

Description Saikat Guha 2010-08-13 18:19:56 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-afc --spawner :1.9 /org/gtk/gvfs/exec_spaw/26
comment: Nothing. It crashed randomly while I was listening to music (from an iPhone using Rhythmbox) and ABRT popped up.
component: gvfs
crash_function: command_read_cb
executable: /usr/libexec/gvfsd-afc
global_uuid: 1de2db8fa73d1f4217b9953249ad9474a0f1e614
kernel: 2.6.33.6-147.2.4.fc13.x86_64
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)
How to reproduce: 1.Randomly crashed
Comment 1 Saikat Guha 2010-08-13 18:19:59 UTC 
Created attachment 438735 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 14:21:25 UTC 

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

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