Bug#772717: bluez: A2DP cannot work immediately after boot.
Sorry, please ignore my last comment. I enabled auto-login for my user in Gnome and didn't need the mentioned workaround. When I disable auto- login I can still reproduce this bug. Tianming Xie, are we affected by the same bug? I don't want to reassign the report to PulseAudio since I'm not the original reporter.
Bug#772717: bluez: A2DP cannot work immediately after boot.
I can't reproduce this bug anymore.
Bug#772717: bluez: A2DP cannot work immediately after boot.
Here's the upstream pulseaudio bug report: https://bugs.freedesktop.org/show_bug.cgi?id=90490
Bug#772717: bluez: A2DP cannot work immediately after boot.
Even more interesting is an upstream gnome-bluetooth bug report [1]. As I understand it, the pulseaudio module module-bluetooth-discover [2] is responsible for detecting available bluetooth audio devices using BlueZ. GDM starts a pulseaudio process [3] before the user does and module-bluetooth-discover in fact works - but for the GDM pulseaudio process, not the one that gets started with X11. I verified that by connecting my bluetooth speakers in GDM (I can connect to the last used paired device with a button). After connecting the speakers, GDM used them for audio output immediately. When I comment out module-bluetooth-discover in /etc/pulse/default.pa as described in Comment 1 in the upstream gnome-bluetooth bug report [1] and then add it to /usr/bin/start-pulseaudio-x11, the bluetooth speakers get detected without any problems and are listed in gnome- control-center audio settings. So in my view this is no BlueZ bug. I think it would make sense to reassign it to PulseAudio. [1] https://bugzilla.gnome.org/show_bug.cgi?id=749208 [2] https://wiki.freedesktop.org/www/Software/PulseAudio/Documentation/ User/Modules/#index35h3 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414
Bug#772717: bluez: A2DP cannot work immediately after boot.
Please have a look at Bug #805414. At least in my case this problem was apparently caused by GDM capturing the A2DP sink. After following the guide in the Debian wiki to prevent GDM from capturing the A2DP sink on session start [1] I can't reproduce this bug anymore. [1] https://wiki.debian.org/BluetoothUser/a2dp#Troubleshooting
Bug#772717: bluez: A2DP cannot work immediately after boot.
I guess I'm affected by this bug, my report (originally reported against pulseaudio) was merged with this one. I tested this with two different notebooks (internal bluetooth adapters: Intel Wireless-N 1030 / Qualcomm Atheros AR5B22). In my original report I attached a bluetoothd log file. > If I reconnect the > bluetooth dongle (tested on a csr dongle with id 0a12:0001 and a broadcom > BCM2046B1 dongle with id 0a5c:21e2, which is a multi-head device, along with a > pair of pseudo-hci kb and mouse), or restart the bluetooth daemon, a2dp > devices > can work like a charm (adding audio sink to pulseaudio works fine). If I > connect the dongle to a cardbus usb host controller (rather than the host > controller embedded in motherboard), which will only be powered and work after > the kernel being booted, a2dp devices work fine. > > It seems a2dp does not work properly if the dongle is powered before > the kernel being booted. Does it always work for you (adding audio sink to pulseaudio) when you restart the bluetooth daemon? In my case sometimes it works (~80%), sometimes it doesn't (~20%). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772717: bluez: A2DP cannot work immediately after boot.
Package: bluez Version: 5.23-2 Severity: normal Dear Maintainer, On my computers, bluetooth mice work fine, but a2dp devices can only be paired and connected to host's bluetooth stack, after which the new audio sink cannot be added to pulseaudio. The phenomenon can only occur after the boot. If I reconnect the bluetooth dongle (tested on a csr dongle with id 0a12:0001 and a broadcom BCM2046B1 dongle with id 0a5c:21e2, which is a multi-head device, along with a pair of pseudo-hci kb and mouse), or restart the bluetooth daemon, a2dp devices can work like a charm (adding audio sink to pulseaudio works fine). If I connect the dongle to a cardbus usb host controller (rather than the host controller embedded in motherboard), which will only be powered and work after the kernel being booted, a2dp devices work fine. It seems a2dp does not work properly if the dongle is powered before the kernel being booted. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluez depends on: ii dbus 1.8.12-1 ii init-system-helpers 1.22 ii kmod 18-3 ii libc62.19-13 ii libdbus-1-3 1.8.12-1 ii libglib2.0-0 2.42.1-1 ii libreadline6 6.3-8+b2 ii libudev1 215-7 ii lsb-base 4.1+Debian13+nmu1 ii udev 215-7 bluez recommends no packages. bluez suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
