Bug 1038235

Summary: [abrt] bluez-5.11-1.fc20: avrcp_handle_register_notification: Process /usr/libexec/bluetooth/bluetoothd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: fred <fredoche>
Component: bluezAssignee: Don Zickus <dzickus>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dwmw2, dzickus, kalevlember, marcel
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/09d6901f888f8f7c8e6207ab73979d2554ab8c46
Whiteboard: abrt_hash:a723e3a6a97a76b5c63e9b8e854c30beeb25eee6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:23:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description fred 2013-12-04 16:50:08 UTC 
Description of problem:
I tried to connect to a nexus 4 phone. Also , my bluetooth dongle is pretty old.

Version-Release number of selected component:
bluez-5.11-1.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/bluetooth/bluetoothd
crash_function: avrcp_handle_register_notification
executable:     /usr/libexec/bluetooth/bluetoothd
kernel:         3.11.10-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 avrcp_handle_register_notification at profiles/audio/avrcp.c:1423
 #1 handle_vendordep_pdu at profiles/audio/avrcp.c:1678
 #2 session_cb at profiles/audio/avctp.c:977
Comment 1 fred 2013-12-04 16:50:18 UTC 
Created attachment 832747 [details]
File: backtrace
Comment 2 fred 2013-12-04 16:50:23 UTC 
Created attachment 832748 [details]
File: cgroup
Comment 3 fred 2013-12-04 16:50:30 UTC 
Created attachment 832749 [details]
File: core_backtrace
Comment 4 fred 2013-12-04 16:50:37 UTC 
Created attachment 832750 [details]
File: dso_list
Comment 5 fred 2013-12-04 16:50:42 UTC 
Created attachment 832751 [details]
File: environ
Comment 6 fred 2013-12-04 16:50:46 UTC 
Created attachment 832752 [details]
File: exploitable
Comment 7 fred 2013-12-04 16:50:49 UTC 
Created attachment 832753 [details]
File: limits
Comment 8 fred 2013-12-04 16:50:54 UTC 
Created attachment 832754 [details]
File: maps
Comment 9 fred 2013-12-04 16:50:58 UTC 
Created attachment 832755 [details]
File: open_fds
Comment 10 fred 2013-12-04 16:51:01 UTC 
Created attachment 832756 [details]
File: proc_pid_status
Comment 11 fred 2013-12-04 16:51:07 UTC 
Created attachment 832757 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 09:55:01 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 13 Fedora End Of Life 2015-06-29 13:23:42 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.