https://bugs.freedesktop.org/show_bug.cgi?id=49974
--- Comment #6 from vlsd <[email protected]> --- I've been using the workaround described here for the past few months with great success: https://bbs.archlinux.org/viewtopic.php?id=165741 This workaround has now stopped working. Instead I can connect the A2DP profile in blueman and the pulseaudio log shows that it registers the new device: D: [pulseaudio] bluetooth-util.c: Device /org/bluez/28447/hci0/dev_00_1D_BA_29_50_D3 interface org.bluez.AudioSink property 'State' changed to value 'connected' D: [pulseaudio] bluetooth-util.c: Device /org/bluez/28447/hci0/dev_00_1D_BA_29_50_D3 interface org.bluez.Audio property 'State' changed to value 'connected' but the device does not appear in pavucontrol. If I connect the headset profile I get similar messages about org.bluez.Headset but the device actually appears and I can send sound to it. The menu then offers me an option to change the profile to a2dp but when I try and do so it fails silently in pavucontrol and the log shows: W: [pulseaudio] module-bluetooth-device.c: Profile not connected, refused to switch profile to a2dp The full log can be found here http://sprunge.us/EHFQ -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
