[pulseaudio-discuss] pulseadio 5 + BlueZ4.101: Sink device not created

[Tanu Kaskinen]

On Tue, 2014-10-28 at 11:14 +0000, tony wrote:
> 
> On 28/10/14 09:44, Tanu Kaskinen wrote:
> > On Thu, 2014-10-23 at 15:57 +0100, tony wrote:
> >> Hi,
> >>         I am trying to get A2DP(BlueZ 4.101) working with Pulseaudio
> >> (pulseaudio 5.0-dirty). I can see the A2DP connection is made
> >> successfully and pulseaudio receives the notification. But for some
> >> reason, can't get pulseaudio to create sink device.
> >>
> >> Following are the last few pulseaudio logs
> >>
> >> D: [pulseaudio] bluez4-util.c: Device
> >> /org/bluez/376/hci0/dev_00_22_37_20_C2_E7 interface org.bluez.AudioSink
> >> property 'State' changed to value 'connecting'
> >> D: [pulseaudio] bluez4-util.c: dbus: interface=org.bluez.Audio,
> >> path=/org/bluez/376/hci0/dev_00_22_37_20_C2_E7, member=PropertyChanged
> >> D: [pulseaudio] bluez4-util.c: Device
> >> /org/bluez/376/hci0/dev_00_22_37_20_C2_E7 interface org.bluez.Audio
> >> property 'State' changed to value 'connecting'
> >> D: [pulseaudio] bluez4-util.c: dbus: interface=org.bluez.AudioSink,
> >> path=/org/bluez/376/hci0/dev_00_22_37_20_C2_E7, member=PropertyChanged
> >> D: [pulseaudio] bluez4-util.c: dbus: interface=org.bluez.AudioSink,
> >> path=/org/bluez/376/hci0/dev_00_22_37_20_C2_E7, member=PropertyChanged
> >> D: [pulseaudio] bluez4-util.c: Device
> >> /org/bluez/376/hci0/dev_00_22_37_20_C2_E7 interface org.bluez.AudioSink
> >> property 'State' changed to value 'connected'
> >> D: [pulseaudio] bluez4-util.c: dbus: interface=org.bluez.Audio,
> >> path=/org/bluez/376/hci0/dev_00_22_37_20_C2_E7, member=PropertyChanged
> >> D: [pulseaudio] bluez4-util.c: Device
> >> /org/bluez/376/hci0/dev_00_22_37_20_C2_E7 interface org.bluez.Audio
> >> property 'State' changed to value 'connected'
> >>
> >>
> >> Following are bluetooth related modules loaded (edited for readability)
> >>
> >> pulseaudio --dump-modules | grep blue
> >> module-bluetooth-discover
> >> module-bluetooth-policy
> >> module-bluez4-device
> >> module-bluez4-discover
> >
> > This command lists all available modules, not only those that are
> > currently loaded. Can you attach the output of "pactl list" and the full
> > log? (Or use a pastebin service, since the log will probably be so big
> > that it will get stuck in the mailing list moderation queue).
> >
> 
> Thank you for helping me with this. Please find full pulseaudio log 
> attached at
> http://pastebin.com/MgdyJTVJ
> and output of 'pactl list' in
> http://pastebin.com/hLjkPQuN

Unfortunately I couldn't find any clues from the log why it doesn't
work. As was already visible in the log snippet in the first mail,
PulseAudio sees both Audio and AudioSink state changing to "connected",
and that should trigger loading of module-bluez4-device, but that just
doesn't seem to happen. I have no clue why.

-- 
Tanu