Hi Georg, On Thu, Jun 20, 2013 at 5:02 PM, Georg Chini <georg at chini.tk> wrote: > Hello, > > after upgrading to Pulseaudio 4.0 my bluetooth devices (headset, 2 mobiles) > are no longer discovered. I am running Debian unstable on an amd64 CPU, > the new Debian package was released a few days ago. > I also filed a bug with Debian but did not receive a reply so far. To make > sure > this is not a problem of the package I compiled pulse from GIT. > I also made sure, that that the headset is properly connected by using ALSA > to play something. This worked fine. Pulseaudio 2.0 discovered the devices > when I connected them. Running Pulse with debug output gives slightly > different results, if "Media" is enabled in Bluez or not. Bluez version is > 4.99. > > With Media enabled: > > During startup: > > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.AudioSink > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Audio > property 'State' changed to value 'disconnected' > > And when I connect the headset: > > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Device, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Device, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'connecting' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Audio > property 'State' changed to value 'connecting' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=SetConfiguration > D: [lt-pulseaudio] module-console-kit.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=SetConfiguration > D: [lt-pulseaudio] bluetooth-util.c: dbus: path=/MediaEndpoint/HFPAG, > interface=org.bluez.MediaEndpoint, member=SetConfiguration > D: [lt-pulseaudio] bluetooth-util.c: Transport > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E/fd40 profile 2 available This seems a successful connection of HSP/HFP. The module is however not loaded because the overall connection procedure (org.bluez.Audio) is still ongoing, and therefore the load of the module is postponed. > D: [lt-pulseaudio] bluetooth-util.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=SetConfiguration > D: [lt-pulseaudio] module-console-kit.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=SetConfiguration > D: [lt-pulseaudio] bluetooth-util.c: dbus: path=/MediaEndpoint/HFPAG, > interface=org.bluez.MediaEndpoint, member=SetConfiguration > E: [lt-pulseaudio] bluetooth-util.c: Cannot configure transport > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E/fd41 because profile 2 is already > used You hit the first issue here. It looks to me that BlueZ is starting the connection procedure twice, for the same profile, using a different transport. This looks like a bug in BlueZ. Any chance you can upgrade to 4.101? I've had a look at the commits between 4.99 and 4.101 and there seem to be a bunch of fixes which could be related to this issue. > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Audio > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=ClearConfiguration > D: [lt-pulseaudio] module-console-kit.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=ClearConfiguration > D: [lt-pulseaudio] bluetooth-util.c: dbus: path=/MediaEndpoint/HFPAG, > interface=org.bluez.MediaEndpoint, member=ClearConfiguration > D: [lt-pulseaudio] bluetooth-util.c: Clearing transport > /org/bluez/7417/hci1/dev_00_19_7F_41_DB_2E/fd40 profile 2 > D: [lt-pulseaudio] bluetooth-util.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=ClearConfiguration > D: [lt-pulseaudio] module-console-kit.c: dbus: > interface=org.bluez.MediaEndpoint, path=/MediaEndpoint/HFPAG, > member=ClearConfiguration > D: [lt-pulseaudio] bluetooth-util.c: dbus: path=/MediaEndpoint/HFPAG, > interface=org.bluez.MediaEndpoint, member=ClearConfiguration > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=(null), path=(null), > member=(null) > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=(null), > path=(null), member=(null) > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=(null), path=(null), > member=(null) > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=(null), > path=(null), member=(null) > > > Doing the same with Media disabled: Media should always be enabled with PA >= 3.0. Cheers, Mikel > During startup (no change): > > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.AudioSink > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'disconnected' > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Audio > property 'State' changed to value 'disconnected' > > When I connect the headset: > > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Device, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Device, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'connecting' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Audio > property 'State' changed to value 'connecting' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Headset > property 'State' changed to value 'connected' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: property 'SpeakerGain' changed to > value '8' > E: [lt-pulseaudio] bluetooth-util.c: Volume change does not have an > associated transport > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.AudioSink, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.AudioSink > property 'State' changed to value 'connecting' > D: [lt-pulseaudio] module-console-kit.c: dbus: > interface=org.bluez.AudioSink, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.AudioSink, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] module-console-kit.c: dbus: > interface=org.bluez.AudioSink, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.AudioSink, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.AudioSink > property 'State' changed to value 'connected' > D: [lt-pulseaudio] module-console-kit.c: dbus: > interface=org.bluez.AudioSink, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: Device > /org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E interface org.bluez.Audio > property 'State' changed to value 'connected' > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Audio, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > > Each time I press one of the volume buttons of the headset I get: > > D: [lt-pulseaudio] bluetooth-util.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > D: [lt-pulseaudio] bluetooth-util.c: dbus: property 'SpeakerGain' changed to > value '6' > E: [lt-pulseaudio] bluetooth-util.c: Volume change does not have an > associated transport > D: [lt-pulseaudio] module-console-kit.c: dbus: interface=org.bluez.Headset, > path=/org/bluez/7939/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged > > > So it seems that pulse does see the headset, but does not load > module-bluetooth-device. > Loading the module manually does not help, pulse does not recognize that the > headset is > connected. > > I hope someone can help me to figure out what goes wrong. Anything more I > should try? > Any config options that have changed from 2.0 to 4.0? If it is a bug, what > can I do to find > out where the problem is? > > Thanks in advance for any help. > > Regards > Georg > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
