It seems some of the issues I was having seem to have stemmed from being in standby mode and resuming thereafter.
>From a clean boot, here's my current steps/output to get the BT device working: 1. Power on system, wait to 'settle': May 21 15:00:46 chrispad bluetoothd[832]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/HFPAG May 21 15:00:46 chrispad bluetoothd[832]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/HFPHS May 21 15:00:46 chrispad bluetoothd[832]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSource May 21 15:00:46 chrispad bluetoothd[832]: Endpoint registered: sender=:1.49 path=/MediaEndpoint/A2DPSink May 21 15:00:47 chrispad dbus[733]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) May 21 15:00:47 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/HFPAG May 21 15:00:47 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/HFPHS May 21 15:00:47 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSource May 21 15:00:47 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.49 path=/MediaEndpoint/A2DPSink May 21 15:00:47 chrispad blueman-mechanism: Starting blueman-mechanism May 21 15:00:47 chrispad dbus[733]: [system] Successfully activated service 'org.blueman.Mechanism' May 21 15:00:47 chrispad blueman-mechanism: loading Network May 21 15:00:47 chrispad blueman-mechanism: loading Config May 21 15:00:47 chrispad blueman-mechanism: loading Ppp May 21 15:00:47 chrispad blueman-mechanism: loading RfKill May 21 15:01:05 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/HFPAG May 21 15:01:05 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/HFPHS May 21 15:01:05 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource May 21 15:01:05 chrispad bluetoothd[832]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink May 21 15:01:05 chrispad bluetoothd[832]: hci0: Remove UUID (0x0011) failed: Busy (0x0a) May 21 15:01:17 chrispad blueman-mechanism: Exiting 2. Load bluetooth-discover: $ pactl load-module module-bluetooth-discover 23 May 21 15:01:28 chrispad bluetoothd[832]: Endpoint registered: sender=:1.63 path=/MediaEndpoint/HFPAG May 21 15:01:28 chrispad bluetoothd[832]: Endpoint registered: sender=:1.63 path=/MediaEndpoint/HFPHS May 21 15:01:28 chrispad bluetoothd[832]: Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource May 21 15:01:28 chrispad bluetoothd[832]: Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSink 3. Power on Bluetooth device (headset connection is started, then terminated): May 21 15:02:04 chrispad bluetoothd[832]: /org/bluez/832/hci0/dev_00_16_94_0B_94_FA/fd0: fd(25) ready May 21 15:02:04 chrispad rtkit-daemon[1390]: Successfully made thread 2301 of process 1968 (n/a) owned by '1000' RT at priority 5. May 21 15:02:04 chrispad rtkit-daemon[1390]: Supervising 4 threads of 1 processes of 1 users. May 21 15:02:07 chrispad bluetoothd[832]: Connection refused (111) May 21 15:02:10 chrispad bluetoothd[832]: Audio connection got disconnected 4. Press 'play' button on Bluetooth device (initiates ad2p?): May 21 15:02:17 chrispad bluetoothd[832]: /org/bluez/832/hci0/dev_00_16_94_0B_94_FA/fd1: fd(26) ready May 21 15:02:17 chrispad rtkit-daemon[1390]: Successfully made thread 2303 of process 1968 (n/a) owned by '1000' RT at priority 5. May 21 15:02:17 chrispad rtkit-daemon[1390]: Supervising 4 threads of 1 processes of 1 users. May 21 15:02:17 chrispad kernel: [ 127.156924] input: 00:16:94:0B:94:FA as /devices/virtual/input/input18 After that, I get AD2P audio available on my headset. I tried this same procedure with an AD2P-only speaker setup, and it works as well after selecting Connect -> Audio Sink in blueman. The interesting thing here is that it seems to load this module during startup, then unload it again a few seconds later. Curious as to why that might be, but I agree, that does seem to resolve the issue. I'll check how it works during standby/sleep and report as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1199059 Title: blueman and pulse's module-bluetooth-discover (A2DP audio sink devices failed to work with "bluetoothd : Unable to select SEP" in system log.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1199059/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
