(In reply to Slava Grig from comment #15)
> Is there any chance to solve this in 2017? How can I help with this? (I'm a
> programmer). Is is a bug of pulseaudio or blueZ?
If you're a programmer, you can dive into pulseaudio and bluez code and figure out why it's not working.
Have you disabled bluetooth for gdm, as hinted to in comment #13? Ruling out the gdm problem would be the first step.
If the a2dp profile in "pactl list cards" shows up as "available: no", then it's likely a bluez bug. An "unavailable" bluetooth profile in pulseaudio means that bluez tells pulseaudio that the profile isn't connected.
(In reply to Slava Grig from comment #15)
> Is there any chance to solve this in 2017? How can I help with this? (I'm a
> programmer). Is is a bug of pulseaudio or blueZ?
If you're a programmer, you can dive into pulseaudio and bluez code and figure out why it's not working.
Have you disabled bluetooth for gdm, as hinted to in comment #13? Ruling out the gdm problem would be the first step.
If the a2dp profile in "pactl list cards" shows up as "available: no", then it's likely a bluez bug. An "unavailable" bluetooth profile in pulseaudio means that bluez tells pulseaudio that the profile isn't connected.