Bug 643759 - [abrt] obex-data-server-1:0.4.5-1.fc13: Process /usr/bin/obex-data-server was killed by signal 11 (SIGSEGV)
Summary: [abrt] obex-data-server-1:0.4.5-1.fc13: Process /usr/bin/obex-data-server was...
Keywords:
Status: CLOSED DUPLICATE of bug 596576
Alias: None
Product: Fedora
Classification: Fedora
Component: obex-data-server
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fea4a7d1645bb7e9681db1232f5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-17 21:43 UTC by Paulo Castro
Modified: 2010-11-08 18:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:04:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (16.21 KB, text/plain)
2010-10-17 21:43 UTC, Paulo Castro
no flags Details

Description Paulo Castro 2010-10-17 21:43:20 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/obex-data-server --no-daemon ''
comment: The file seems to reach it's destiny in it's integral form. The obex server seems to crash after that.
component: obex-data-server
crash_function: IA__g_type_check_instance_cast
executable: /usr/bin/obex-data-server
kernel: 2.6.36-rc7PEC12-00089-g00d741b
package: obex-data-server-1:0.4.5-1.fc13
rating: 4
reason: Process /usr/bin/obex-data-server was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1287351633
uid: 500

How to reproduce
-----
1.Open /usr/bin/kbluetooth
2.Send a file to a device
3.

Comment 1 Paulo Castro 2010-10-17 21:43:22 UTC
Created attachment 453966 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:04:03 UTC

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

Comment 3 Karel Klíč 2010-11-08 18:04:03 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 #596576.

Sorry for the inconvenience.


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