Bug#712601: After upgrading pulseaudio from 2.0 to 4.0 Bluetooth devices are no longer recognized
Georg Chini
georg at chini.tk
Mon Jun 17 19:24:17 UTC 2013
Package: pulseaudio
Version: 4.0-3
Severity: important
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9.4 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pulseaudio depends on:
ii adduser 3.113+nmu3
ii consolekit 0.4.5-3.1
ii libasound2 1.0.27.1-1
ii libasound2-plugins 1.0.27-2
ii libc6 2.17-5
ii libcap2 1:2.22-1.2
ii libdbus-1-3 1.6.12-1
ii libfftw3-single3 3.3.3-5
ii libgcc1 1:4.8.1-3
ii libice6 2:1.0.8-2
ii libltdl7 2.4.2-1.2
ii liborc-0.4-0 1:0.4.17-2
ii libpulse0 4.0-3
ii libsamplerate0 0.1.8-5
ii libsm6 2:1.2.1-2
ii libsndfile1 1.0.25-5
ii libspeexdsp1 1.2~rc1-7
ii libstdc++6 4.8.1-3
ii libsystemd-login0 44-11
ii libtdb1 1.2.10-2
ii libudev0 175-7.2
ii libwebrtc-audio-processing-0 0.1-2
ii libx11-6 2:1.6.0-1
ii libx11-xcb1 2:1.6.0-1
ii libxcb1 1.9.1-3
ii libxtst6 2:1.2.1-1+deb7u1
ii lsb-base 4.1+Debian12
ii udev 175-7.2
Versions of packages pulseaudio recommends:
ii gstreamer0.10-pulseaudio 0.10.31-3+nmu1
ii pulseaudio-module-x11 4.0-3
ii rtkit 0.10-2
Versions of packages pulseaudio suggests:
pn paman <none>
pn paprefs <none>
ii pavucontrol 1.0-1
pn pavumeter <none>
ii pulseaudio-utils 4.0-3
-- Configuration Files:
/etc/pulse/daemon.conf changed [not included / minor changes]
/etc/pulse/default.pa changed [not included /minor changes]
/etc/pulse/system.pa changed [not included / not used]
After upgrading to pulseaudio 4.03 my bluetooth devices are no longer
recognized by pulse.
Running pulseaudio with debug logging shows the following output in the
log when I connect a headset:
bluetooth-util.c: dbus: interface=org.bluez.Device,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
module-console-kit.c: dbus: interface=org.bluez.Device,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
bluetooth-util.c: dbus: interface=org.bluez.Headset,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
bluetooth-util.c: Device /org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E
interface org.bluez.Headset property 'State' changed to value 'connecting'
module-console-kit.c: dbus: interface=org.bluez.Headset,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
bluetooth-util.c: dbus: interface=org.bluez.Audio,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
bluetooth-util.c: Device /org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E
interface org.bluez.Audio property 'State' changed to value 'connecting'
module-console-kit.c: dbus: interface=org.bluez.Audio,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
bluetooth-util.c: dbus: interface=org.bluez.Headset,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
bluetooth-util.c: Device /org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E
interface org.bluez.Headset property 'State' changed to value 'connected'
module-console-kit.c: dbus: interface=org.bluez.Headset,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
bluetooth-util.c: dbus: interface=org.bluez.Headset,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
module-console-kit.c: dbus: interface=org.bluez.Headset,
path=/org/bluez/4382/hci1/dev_00_19_7F_41_DB_2E, member=PropertyChanged
The headset does not show up in pavucontrol or pacmd list-cards. The
same happens for my mobiles. Manually loading module-bluetooth-device
(with address=....) does not help. Same configuration worked fine with 2.0
More information about the pkg-pulseaudio-devel
mailing list