Bug 1109486 - [abrt] bluez: avdtp_get_device(): bluetoothd killed by SIGSEGV
Summary: [abrt] bluez: avdtp_get_device(): bluetoothd killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Don Zickus
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:ab7bb82e828905344d50eb174d1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-14 12:17 UTC by Joshua Rich
Modified: 2015-06-29 21:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:07:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (13.33 KB, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: cgroup (160 bytes, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: core_backtrace (3.77 KB, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: dso_list (1.26 KB, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: environ (120 bytes, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: exploitable (82 bytes, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: maps (6.18 KB, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: open_fds (1.21 KB, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: proc_pid_status (905 bytes, text/plain)
2014-06-14 12:17 UTC, Joshua Rich
no flags Details
File: var_log_messages (3.04 KB, text/plain)
2014-06-14 12:18 UTC, Joshua Rich
no flags Details

Description Joshua Rich 2014-06-14 12:17:35 UTC
Version-Release number of selected component:
bluez-5.18-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/bluetooth/bluetoothd
crash_function: avdtp_get_device
executable:     /usr/libexec/bluetooth/bluetoothd
kernel:         3.14.7-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 avdtp_get_device at profiles/audio/avdtp.c:3832
 #1 auto_config at profiles/audio/a2dp.c:382
 #2 media_endpoint_cancel at profiles/audio/media.c:136
 #3 media_endpoint_cancel_all at profiles/audio/media.c:144
 #4 clear_endpoint at profiles/audio/media.c:245
 #5 endpoint_reply at profiles/audio/media.c:275
 #6 complete_pending_call_and_unlock at dbus-connection.c:2314
 #8 message_dispatch at gdbus/mainloop.c:72

Comment 1 Joshua Rich 2014-06-14 12:17:40 UTC
Created attachment 908770 [details]
File: backtrace

Comment 2 Joshua Rich 2014-06-14 12:17:43 UTC
Created attachment 908771 [details]
File: cgroup

Comment 3 Joshua Rich 2014-06-14 12:17:44 UTC
Created attachment 908772 [details]
File: core_backtrace

Comment 4 Joshua Rich 2014-06-14 12:17:46 UTC
Created attachment 908773 [details]
File: dso_list

Comment 5 Joshua Rich 2014-06-14 12:17:49 UTC
Created attachment 908774 [details]
File: environ

Comment 6 Joshua Rich 2014-06-14 12:17:50 UTC
Created attachment 908775 [details]
File: exploitable

Comment 7 Joshua Rich 2014-06-14 12:17:53 UTC
Created attachment 908776 [details]
File: limits

Comment 8 Joshua Rich 2014-06-14 12:17:55 UTC
Created attachment 908777 [details]
File: maps

Comment 9 Joshua Rich 2014-06-14 12:17:57 UTC
Created attachment 908778 [details]
File: open_fds

Comment 10 Joshua Rich 2014-06-14 12:17:59 UTC
Created attachment 908779 [details]
File: proc_pid_status

Comment 11 Joshua Rich 2014-06-14 12:18:01 UTC
Created attachment 908780 [details]
File: var_log_messages

Comment 12 olivier.devroede 2014-12-02 13:26:58 UTC
Another user experienced a similar problem:

trying to connect to a blutooth device made the error happen. I run the latest KDE

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/bluetooth/bluetoothd
crash_function: avdtp_get_device
executable:     /usr/libexec/bluetooth/bluetoothd
kernel:         3.17.3-200.fc20.x86_64
package:        bluez-5.18-1.fc20
reason:         bluetoothd killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 Fedora End Of Life 2015-05-29 12:06:50 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2015-06-29 21:07:18 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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