Bluetooth loops when pairing Connecting MPOW T5 headset

[Johnny Ooi]

I am running ubuntu Disco, recently upgraded from Beaver.

Now when I pair my MPOW T5 bluetooth earbuds, they will pair, connect, then Bluetooth on the machine will restart. This is visible by the Bluetooth applet showing Bluetooth being switched off then on again. This will happen a few times, then bluetooth will lock up, rendering it and the settings applet frozen. Requiring a restart to fix.

It is like something in Bluetooth subsystem is crashing out when pairing with the T5

I used to use this MPOW T5 with ubuntu Beaver without issue and am tempted just to roll back to my image from then But here's hoping someone can help identify why this is happening.

I am also using this on my Disco installation on my Pixelbook (which was a clean install, not an upgrade), so maybe that's something worth noting.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: johnny 2201 F.... pulseaudio
 /dev/snd/controlC0: johnny 2201 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 27 17:34:49 2019
InstallationDate: Installed on 2018-12-31 (269 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: Upgraded to disco on 2019-09-21 (6 days ago)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W35xSS_370SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W35xSS_370SS
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: johnny 2878 F.... pulseaudio
 /dev/snd/controlC0: johnny 2878 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2018-12-31 (352 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Notebook W35xSS_370SS
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-37.40-generic 5.0.21
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-37-generic N/A
 linux-backports-modules-5.0.0-37-generic N/A
 linux-firmware 1.178.6
Tags: disco
Uname: Linux 5.0.0-37-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-09-21 (89 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W35xSS_370SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W35xSS_370SS
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

[Johnny Ooi (johnny-jy-ooi+launchpad)]

As an experiment took the 19.04 Ubuntu live disk, booted up from that and paired mt MPOW T5. Bluetooth crash looped as well. This eliminates anything I've installed as cause.

I suspect something in the driver is not liking the bluetooth device on my machine, since it paired with 19.04 on my Pixelbook okay without crash looping.

[Johnny Ooi (johnny-jy-ooi+launchpad)]

Oh, and it pairs okay under Windows on the same laptop (I dual boot Windows 8 and Ubuntu)

[Johnny Ooi (johnny-jy-ooi+launchpad)]

More details that might help debugging. Found this in the syslog:

Dec 18 18:58:21 johnny-W35xSS-370SS systemd[1]: systemd-rfkill.service: Succeeded.
Dec 18 18:58:24 johnny-W35xSS-370SS kernel: [ 336.791201] input: 00:20:5B:12:1F:B6 as /devices/virtual/input/input34
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) config/udev: Adding input device 00:20:5B:12:1F:B6 (/dev/input/event20)
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 00:20:5B:12:1F:B6: Applying InputClass "libinput keyboard catchall"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) Using input driver 'libinput' for '00:20:5B:12:1F:B6'
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) systemd-logind: got fd for /dev/input/event20 13:84 fd 70 paused 0
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 00:20:5B:12:1F:B6: always reports core events
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "Device" "/dev/input/event20"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "_source" "server/udev"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device is a keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device removed
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input34/event20"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) XINPUT: Adding extended input device "00:20:5B:12:1F:B6" (type: KEYBOARD, id 18)
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_model" "pc105"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_layout" "gb"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_variant" "extd"
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (WW) Option "xkb_options" requires a string value
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device is a keyboard
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
De...

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue looks like rather a kernel one

kernel: [ 353.504506] usb 3-7: Failed to suspend device, error -71

Would be useful to also get a bluetooth -d debug log

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1845689

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

apport information

[Johnny Ooi (johnny-jy-ooi+launchpad)]

@seb128 re the bluetooth log, how do I obtain that? I've done the apport stuff, does that include the bluetooth log?

[Johnny Ooi (johnny-jy-ooi+launchpad)]

Marking as confirmed as instructed

[Kai-Heng Feng (kaihengfeng)]

Can you please test 20.04 daily image?
http://cdimages.ubuntu.com/daily-live/current/

[Johnny Ooi (johnny-jy-ooi+launchpad)]

Hi, the same problem occurs, even using a different MPOW model and an Anker brand.

I've attached the syslog output in another file

[Kai-Heng Feng (kaihengfeng)]

Can you please test v4.15 based kernel, which is used in Bionic Beaver?

[Johnny Ooi (johnny-jy-ooi+launchpad)]

Okay, will dig out my old backup images and see.

[Johnny Ooi (johnny-jy-ooi+launchpad)]

My only backup image was from 17.10, running kernel Kernel 4.13.0-46-generic.

I stand corrected on the earbud model. It was an MPOW Flame that time, and not an MPOW T5/M5 model

Nonetheless, even in the 17.10 backup image, bluetooth restarts.

However, unlike in Disco, my earbuds actually manage to connect. The connection does drop after a couple of seconds, however.

Also, I did find something that may be of relevance.

I have an old USB Bluetooth dongle. And I plugged that in, and then used Blueman-manager to switch to that adapter and pair my earbuds -- and it works.

Does this help further debugging?