Bug 770862 - [abrt] gvfs-obexftp-1.6.4-2.fc14: Process /usr/libexec/gvfsd-obexftp was killed by signal 11 (SIGSEGV)
Summary: [abrt] gvfs-obexftp-1.6.4-2.fc14: Process /usr/libexec/gvfsd-obexftp was kill...
Keywords:
Status: CLOSED DUPLICATE of bug 661635
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a2a1819c9bec3f143ad718fec8b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-29 19:01 UTC by pcdocms
Modified: 2015-03-03 23:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 14:54:52 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (11.56 KB, text/plain)
2011-12-29 19:01 UTC, pcdocms 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description pcdocms 2011-12-29 19:01:28 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.11 /org/gtk/gvfs/exec_spaw/8
component: gvfs
crash_function: pthread_cond_signal@@GLIBC_2.3.2
executable: /usr/libexec/gvfsd-obexftp
kernel: 2.6.35.6-45.fc14.i686
package: gvfs-obexftp-1.6.4-2.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-obexftp was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1325182809
uid: 500

How to reproduce
-----
1. tried to attach to a bluetooth enabled phone
2. attached to the phone
3. attempted to browse files on the phone. program then crashed
Comment 1 pcdocms 2011-12-29 19:01:36 UTC 
Created attachment 549986 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 14:54:52 UTC 
Backtrace analysis found this bug to be similar to bug #661635, closing as duplicate.

Bugs which were found to be similar to this bug: bug #604731, bug #661635, bug #662288

This comment is automatically generated.

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