Your message dated Tue, 10 Jun 2014 12:03:23 -0400
with message-id
<CAAfdZj9JW=pn9ae_7cwbfnk5hngdz2qfthsb9gx4zu3_khd...@mail.gmail.com>
and subject line Closing old bugs
has caused the Debian Bug report #712601,
regarding After upgrading pulseaudio from 2.0 to 4.0 Bluetooth devices are no
longer recognized
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
712601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Hi,
I'm sorry I have to close your bug without a proper fix. However, your
bug is being closed because when asked for more information, over a
month passed without reply, and/or another user reported the bug gone.
If I closed your bug wrongly, please reopen it or file a new one. I
will try to help in debugging the problem.
--
Saludos,
Felipe Sateler
--- End Message ---
_______________________________________________
pkg-pulseaudio-devel mailing list
pkg-pulseaudio-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel
