Bug 611397 - [abrt] crash in obex-data-server-1:0.4.5-1.fc13: obex_io_callback: Process /usr/bin/obex-data-server was killed by signal 11 (SIGSEGV)
[abrt] crash in obex-data-server-1:0.4.5-1.fc13: obex_io_callback: Process /u...
Status: CLOSED DUPLICATE of bug 625874
Product: Fedora
Classification: Fedora
Component: obex-data-server (Show other bugs)
13
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
abrt_hash:bb70e84e1b65d7b6c5afac10114...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-05 02:09 EDT by matius
Modified: 2010-11-08 12:59 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-08 12:59:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (13.05 KB, text/plain)
2010-07-05 02:09 EDT, matius
no flags Details

  None (edit)
Description matius 2010-07-05 02:09:54 EDT
abrt 1.1.1 detected a crash.

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
global_uuid: bb70e84e1b65d7b6c5afac10114094f646c85361
kernel: 2.6.33.5-124.fc13.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 13 (Goddard)
Comment 1 matius 2010-07-05 02:09:57 EDT
Created attachment 429465 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 12:59:52 EST

*** This bug has been marked as a duplicate of bug 625874 ***
Comment 3 Karel Klíč 2010-11-08 12:59:52 EST
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.