Happy update. Resolved my issues with at least the Sennheiser Urbanite
XL Wireless by disconnecting from my android phone before trying to
connect to Ubuntu 16.04. I'll take it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
4 May 10 08:13:07 deathstar systemd[1]: Stopping User Manager for UID 108...
5 May 10 08:13:07 deathstar systemd[1880]: Stopped target Default.
6 May 10 08:13:07 deathstar systemd[1880]: Reached target Shutdown.
7 May 10 08:13:07 deathstar systemd[1880]: Stopped target Basic System.
Tried again just now with the Sennheiser Urbanite XL Wireless and see
this in the syslog:
May 10 08:00:02 deathstar wpa_supplicant[1472]: wlp6s0: Failed to initiate
sched scan
May 10 08:00:09 deathstar rtkit-daemon[2045]: Supervising 4 threads of 1
processes of 1 users.
May 10 08:00:09
Also see this in dmesg:
[ 505.747613] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 505.747616] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 505.747617] Bluetooth: hci0 SCO packet for unknown connection handle 0
[ 510.979305] Bluetooth: hci0 SCO packet for
@maxb: also see this a bit later:
Apr 26 09:40:37 deathstar bluetoothd[1043]: Unable to get Headset Voice
gateway SDP record: Host is down
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
If I run:
sudo systemctl restart bluetooth
the Bluetooth icon in the system taskbar goes blank, and if I try to re-
enable it nothing ever happens. Here's the logs from that state:
Apr 26 09:41:38 deathstar systemd[1]: Stopping Bluetooth service...
Apr 26 09:41:38 deathstar bluetoothd[1043]:
@marc-edcc: ok, that apparently does not work when sleeping the laptop
and resuming ;-(
@maxb: here's how my logs looked when it was failing to connect:
Apr 26 09:37:07 deathstar bluetoothd[1043]: Unable to get io data for Headset
Voice gateway: getpeername: Transport endpoint is not connected
@marc-edcc: your method works the most consistently. I've rebooted
multiple times, connecting and disconnecting the headset with my phone
and other devices, and turning it on and off, and also connecting and
disconnecting from the 16.04 laptop, and I haven't had a single problem
getting audio to
Hah, removing the gnome packages and reverting the configs did not
resolve the issue. Still have to remove the bluetooth device and repair
upon any reboot or resuming from sleep / hibernate. What a pain in the
ass.
--
You received this bug notification because you are a member of Desktop
Another update. I had accidentally installed gnome-tweak-tool on my
unity install instead of unity-tweak-tool, which pulled in a bunch of
gnome-core stuff. After uninstalling the gnome stuff and reverting my
configs to default (i.e. removing everything I did in post #5) my
bluetooth headphones
@mark-edcc thanks for the update. I'll try that in the future if
necessary, but I really feel like the gnome nonsense caused all this.
When I tried the 16.04 beta, it was the gnome flavor, and I experienced
the same nonsense on arch linux with gnome. Never had this problem with
unity. Weird.
Update to this, which might help in diagnosing, might not.
I can ensure that the bluetooth A2DP connection will successfully
deliver audio to my headset consistently if I switch back to "Headset
Head Unit (HSP/HFP)" mode in Sound settings prior to disconnecting the
headset.
Then, next time I
I can confirm that ubuntu 16.04 LTS is exhibiting this behavior with
three separate bluetooth headsets (JABRA REVO 2.0, Sony MDRXB950BT, and
Sennheiser Urbanite XL WIreless).
14.04, 14.10, 15.04, and 15.10 all worked quite well with no additional
configuration necessary. By "worked quite well" I
13 matches
Mail list logo
