Created attachment 588588 [details]
File: backtrace

Created attachment 588589 [details]
File: maps

Created attachment 588590 [details]
File: var_log_messages

1. boot system and logged in.
2. paired bluetooth headset (plantronics) to computer
3. the headset paired up without a problem
4. pulse audio failed


backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

PulseAudio crashes when connecting a Nokia BH-102 Bluetooth Headset

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

I have the same issue as @antman above with a samsung HM3700 and an Arctic P311

I can pair bluetooth audio but when I try to connect, the connection gets terminated within seconds!
Furthermore: Whenever I try to open "audio preferences" during that time from the Bluetooth applet, Pulseaudio crashes.

I suspect there is a general permition problem in f17!

my messages log include:
------------
Jun 14 17:39:13 Chris bluetoothd[8194]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Jun 14 17:39:13 Chris bluetoothd[8194]: Listening for HCI events on hci0
Jun 14 17:39:13 Chris bluetoothd[8194]: HCI dev 0 up
Jun 14 17:39:13 Chris bluetoothd[8194]: l2cap_bind: Address already in use (98)
Jun 14 17:39:13 Chris bluetoothd[8194]: network-server: Invalid argument (22)
Jun 14 17:39:13 Chris bluetoothd[8194]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Jun 14 17:39:13 Chris bluetoothd[8194]: Failed to listen on control channel
Jun 14 17:39:13 Chris bluetoothd[8194]: input-server: Operation not permitted (1)
Jun 14 17:39:13 Chris bluetoothd[8194]: rfcomm_bind: Address already in use (98)
Jun 14 17:39:13 Chris bluetoothd[8194]: audio-headset: Operation not permitted (1)
Jun 14 17:39:13 Chris bluetoothd[8194]: l2cap_bind: Address already in use (98)
Jun 14 17:39:13 Chris bluetoothd[8194]: audio-a2dp: Operation not permitted (1)
Jun 14 17:39:13 Chris bluetoothd[8194]: l2cap_bind: Address already in use (98)
Jun 14 17:39:13 Chris bluetoothd[8194]: audio-control: Operation not permitted (1)
Jun 14 17:39:13 Chris bluetoothd[8194]: Unable to load keys to adapter_ops: Function not implemented (38)
Jun 14 17:39:13 Chris bluetoothd[8194]: Adapter /org/bluez/8193/hci0 has been enabled
Jun 14 17:39:13 Chris bluetoothd[8194]: Endpoint registered: sender=:1.47 path=/MediaEndpoint/HFPAG
Jun 14 17:39:13 Chris bluetoothd[8194]: Inquiry Cancel Failed with status 0x12
------------ 


I assume, this error has one of these two origins:
1) SELinux
2) some other group rights stuff

Workaround found!

Its SELinux's fault!!
disable it and BT Audio is working fine again.

1) add selinux=0 to /etc/boot/grub
2) execute "sudo grub2-mkconfig -o /boot/grub2/grub.cfg"

The workaround from Christian von Behren didn't work for me.   I already had selinux turned off, but I added the grub stuff anyway (to /etc/default/grub) and ran grub2-mkconfig.

Created attachment 591880 [details]
abrt information about this pulseaudio / bluetooth crash

I don't know if this is useful, but it's the abrt information (?) about the crash

Created attachment 591881 [details]
excerpt from /var/log/messages about the crash

while reading through your attachment, it looks like there are two simultanious attempts to connect your device - at least I haven't seen that twice registering stuff before...

----
Jun 14 11:40:02 t420 bluetoothd[639]: Endpoint registered: sender=:1.81 path=/MediaEndpoint/HFPAG
Jun 14 11:40:02 t420 bluetoothd[639]: Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource
---

Furthermore the first one (HFPAG) seems to break pulse just before the device is completly set up:
---
Jun 14 11:40:02 t420 kernel: [  138.433143] pulseaudio[1526]: segfault at 9000000 ip 41a80ad6 sp bfbb1b54 error 4 in libc-2.15.so[419fe000+1a8000]
...
Jun 14 11:40:02 t420 bluetoothd[639]: Badly formated or unrecognized command: AT+CSRSF=0,0,0,0,0,7
Jun 14 11:40:04 t420 bluetoothd[639]: bluetoothd[639]: Unable to select SEP
---

This is only a random thought, but you could try to set a config for the device rather than let the system configure it itself (which obviously fails:

try to set a audio.conf in /etc/bluetooth/ with the following content:
---
Enable=Source,Sink,Headset,Gateway,Control,Socket,Media
HFP=false
---

You will have to create that file (it's not there in default)

I could interpret your logs completely wrong though...
Good luck

forget the first part I wrote before - HFPAG and A2DPSource get registered here exactly the same! the difference is, here it works :-/

Jun 14 18:18:47 Chris bluetoothd[643]: bluetoothd[643]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/HFPAG
Jun 14 18:18:47 Chris bluetoothd[643]: bluetoothd[643]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource
Jun 14 18:18:47 Chris bluetoothd[643]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/HFPAG
Jun 14 18:18:47 Chris bluetoothd[643]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource

so that's no error but the use case..
I have no clue though, why pulse crashes on your machine

someone else?

OK - my workaround is this - create an /etc/bluetooth/audio.conf file with the following lines:


[General]
Disable=Media
Enable=Source,Sink,Headset,Gateway,Control,Socket


I don't have stereo output, but I never use that anyway.  I don't know if anything other than "Headset" is needed in that Enable line.

The control-center app generally crashes at least once when I pair / connect, but pulse is able to stay up.

I had similar problems with a Motorola HT820 headset crashing the pulseaudio daemon.  I used David Wilkins workaround (above), but without the 'Headset' entry, i.e.

create /etc/bluetooth/audio.conf containing the lines

[General]
Disable=Media
Enable=Source,Sink,Gateway,Control,Socket


After restarting, I was able to select either the 'Telephony Duplex (HSP/HFP)' option, or the 'High Fidelity Playback (A2DP)' option in 
System Settings
  Hardware (section)
    Sound
      Hardware (tab)
        Settings for the elected device

Both the Telephony and the High Fidelity mode worked correctly

I have connected one Creative Labs WP-250 Headset (Bluetooth)

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

I tried the workaround suggested in Comment 14. In addition, I had to remove the headset from the known Bluetooth device list, reboot the computer and try to pair again. The headset successfully works now.

connected bluetooth

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

I reported issues with Pulseaudio crashing under similar circumstances in bug #827563 ... My problems have been solved after applying Les' workaround in comment 15! :-D

This problem does not occur for me on my x86_64 system, only on my i686 machine. I notice a few other reporters here are also running 32-bit systems. Is this possibly an architecture-specific problem?

*Happily enjoying my bluetooth headset.*

*** Bug 827563 has been marked as a duplicate of this bug. ***

Crashed after adding a new Bluetooth headset

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

When pairing/activating my bluetooth headset (ProPlantronics) pulseaudio crashes.  Note that earlier experiments of mine show that it crashes when activating the headset device, not when pairing.

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Workaround from comment #15 worked fine

Trying to play audio to Plantronics Savi 170 headset while paired via Bluetooth.

Part of messagelog:
Jul 16 20:20:15 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint registered: sender=:1.101 path=/MediaEndpoint/HFPAG
Jul 16 20:20:15 zaibukas bluetoothd[547]: Endpoint registered: sender=:1.101 path=/MediaEndpoint/HFPAG
Jul 16 20:20:15 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint registered: sender=:1.101 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:15 zaibukas bluetoothd[547]: Endpoint registered: sender=:1.101 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:15 zaibukas abrt[2385]: Not dumping repeating crash in '/usr/bin/pulseaudio'
Jul 16 20:20:15 zaibukas pulseaudio[2370]: [pulseaudio] main.c: Daemon startup failed.
Jul 16 20:20:15 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint unregistered: sender=:1.101 path=/MediaEndpoint/HFPAG
Jul 16 20:20:15 zaibukas bluetoothd[547]: Endpoint unregistered: sender=:1.101 path=/MediaEndpoint/HFPAG
Jul 16 20:20:15 zaibukas bluetoothd[547]: Endpoint unregistered: sender=:1.101 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:15 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint unregistered: sender=:1.101 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:16 zaibukas abrtd: New problem directory /var/spool/abrt/ccpp-2012-07-16-20:20:14-2362, processing
Jul 16 20:20:57 zaibukas rtkit-daemon[1037]: Successfully made thread 2446 of process 2446 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Jul 16 20:20:57 zaibukas pulseaudio[2446]: [pulseaudio] pid.c: Stale PID file, overwriting.
Jul 16 20:20:58 zaibukas rtkit-daemon[1037]: Successfully made thread 2447 of process 2446 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Jul 16 20:20:58 zaibukas rtkit-daemon[1037]: Successfully made thread 2448 of process 2446 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Jul 16 20:20:58 zaibukas pulseaudio[2446]: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
Jul 16 20:20:58 zaibukas pulseaudio[2446]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes card_properties="module-udev-detect.discovered=1""): initialization failed.
Jul 16 20:20:58 zaibukas kernel: [ 3647.602312] pulseaudio[2446]: segfault at 9000008 ip 48d86ad6 sp bfcee104 error 4 in libc-2.15.so[48d04000+1a8000]
Jul 16 20:20:58 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint registered: sender=:1.106 path=/MediaEndpoint/HFPAG
Jul 16 20:20:58 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint registered: sender=:1.106 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:58 zaibukas bluetoothd[547]: Endpoint registered: sender=:1.106 path=/MediaEndpoint/HFPAG
Jul 16 20:20:58 zaibukas bluetoothd[547]: Endpoint registered: sender=:1.106 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:58 zaibukas abrtd: Directory 'ccpp-2012-07-16-20:20:58-2446' creation detected
Jul 16 20:20:58 zaibukas abrt[2449]: Saved core dump of pid 2446 (/usr/bin/pulseaudio) to /var/spool/abrt/ccpp-2012-07-16-20:20:58-2446 (18636800 bytes)
Jul 16 20:20:58 zaibukas pulseaudio[2443]: [pulseaudio] main.c: Daemon startup failed.
Jul 16 20:20:58 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint unregistered: sender=:1.106 path=/MediaEndpoint/HFPAG
Jul 16 20:20:58 zaibukas bluetoothd[547]: bluetoothd[547]: Endpoint unregistered: sender=:1.106 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:58 zaibukas bluetoothd[547]: Endpoint unregistered: sender=:1.106 path=/MediaEndpoint/HFPAG
Jul 16 20:20:58 zaibukas bluetoothd[547]: Endpoint unregistered: sender=:1.106 path=/MediaEndpoint/A2DPSource
Jul 16 20:20:59 zaibukas abrtd: Duplicate: core backtrace
Jul 16 20:20:59 zaibukas abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2012-07-16-20:20:14-2362
Jul 16 20:20:59 zaibukas abrtd: Problem directory is a duplicate of /var/spool/abrt/ccpp-2012-07-16-20:20:14-2362
Jul 16 20:20:59 zaibukas abrtd: Deleting problem directory ccpp-2012-07-16-20:20:58-2446 (dup of ccpp-2012-07-16-20:20:14-2362)


backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

I can confirm that the workaround from comment #15 worked for me on an i686 system.

I applied the workaround from https://bugzilla.redhat.com/show_bug.cgi?id=827629#c14 and it worked for me on x86_64 after systemctl restart bluetooth.service

Pulse Audio crashes when connecting to a bluetooth headset

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Tried to connect paired bluetooth audio device. Pulse crashes on connecting then bluez fails to connect until session restart.

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Bluetooth was already activated. 
I paired a bluetooth headset.
When I attempted to activate the paired headset, pulseaudio blew up. 
There were not other warnings, such as a dialog box with an application error message, to indicate any problem.  
Note that I used a cheap ($5 USD) bluetooth headset intended for cellphone use 
(I was just trying to see if it works with Skype on the laptop).  The headset does
not provide media playback on Android or iPhone cellphones without using bridge 
software, but does work on Nokia phones (or so I'm told).
 


backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

running fedora 17 (3.5.2-1.fc17.i686.PAE) with kde desktop. Attempt to  pair or (re-)connect with a bluetooth stereo headset NUV2882.  this is done via the kde taskbar by clicking on the bluetooth icon (bluedevil-monolithic)-> add device or connect listed device (after initial sucessful pairing)

The moment the bluetooth headset is connected it seems that pulseaudio crashes. 
No audio on playback. pavucontrol not available
Restarting pulseaudio manually makes pulseaudio segfault instantly.

workaround   reboot machine
or   disconnect bluetooth headset and restart pulseaudio

Same problem occurs with Samsung WEP475 bluetooth (mono audio)

PS: Both devices have been working with  Fedora 15


backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

(In reply to comment #30)

I followed the workaround from Comment #14 and/or #15.

----
 create /etc/bluetooth/audio.conf containing the lines

 [General]
 Disable=Media
 Enable=Source,Sink,Gateway,Control,Socket
----

Rebooted the box and now pulseaudio survives when connecting the 
bluetooth headset
And now I am happily listening ;-)

Cannot reproduce this on a fresh install of F18. pulseaudio 2.0-4.fc18

The workaround in comment 15 is working for me too, on Fedora 17 32-bit i686, with Motorola S805 headphones.

Pairing a bluetooth headset with A2DP profile.

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Workaround in comment 15 works on F17 x86 and Nokia BH-503 headset.
Regards

paired blue tooth headset, after pairing completed problem occured.
did  a second try after restarting computer, the headset was paired, clicked connect in bluetooth window,  to connect it then same problem.
headset is an AKG K830BT


backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Crash immideately after pairing to a bluetooth headphone

backtrace_rating: 4
Package: pulseaudio-1.1-9.fc17
OS Release: Fedora release 17 (Beefy Miracle)

I have the same problem trying to connect my Bose A20 headset over bluetooth on Fedora 17.  I tried the #14 and #15 workarounds, creating a /etc/bluetooth/audio.conf file both with and without a 'Headset' item, as cited in https://bugzilla.redhat.com/show_bug.cgi?id=827629#c14 and https://bugzilla.redhat.com/show_bug.cgi?id=827629#c15.  

This did result in no more crashing, and successfully pairing and connecting the device, but:

(1) only in mono, and
(2) NOT in 'High Fidelity Playback (A2DP)'.  The only service that showed up was Telephony Duplex (HSP/HFP)'.

I need to use it for A2DP and stereo, so would be grateful if anybody has any insights?  Many thanks.

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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