Bug 648105 - [abrt] obex-data-server-1:0.4.5-1.fc13: obex_io_callback: Process /usr/bin/obex-data-server was killed by signal 11 (SIGSEGV)
Summary: [abrt] obex-data-server-1:0.4.5-1.fc13: obex_io_callback: Process /usr/bin/ob...
Keywords:
Status: CLOSED DUPLICATE of bug 625874
Alias: None
Product: Fedora
Classification: Fedora
Component: obex-data-server
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:30f1ab60973091370fa0f2193cf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-30 22:40 UTC by Jon Burgess
Modified: 2010-11-08 18:00 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (13.08 KB, text/plain)
2010-10-30 22:40 UTC, Jon Burgess 		no flags Details
View All

Description Jon Burgess 2010-10-30 22:40:12 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/obex-data-server --no-daemon ''
component: obex-data-server
crash_function: obex_io_callback
executable: /usr/bin/obex-data-server
kernel: 2.6.35.6-48.fc14.i686
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 14 (Laughlin)
time: 1288477348
uid: 500

How to reproduce
-----
1. Sent a file to phone via kbluetooth 'send->file' option
2. after sending the file, abrt reported the segv
3.
Comment 1 Jon Burgess 2010-10-30 22:40:15 UTC 
Created attachment 456680 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:00:32 UTC 

*** This bug has been marked as a duplicate of bug 625874 ***
Comment 3 Karel Klíč 2010-11-08 18:00:32 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 #625874.

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