Ubuntu 16.10 bluetooth doesn't work

Bug #1628694 reported by Alex
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I'm trying unsuccessfully to connect headphone via bluetooth. Configuration: Ubuntu-gnome 16:10, Dell XPS-15. lspci shows:

06:00.0 Network controller: Broadcom Limited BCM4352 802.11ac Wireless Network Adapter (rev 03)

lsusb shows:

Bus 003 Device 004: ID 0a5c:216f Broadcom Corp. BCM20702A0 Bluetooth

Below is what I see in my syslog:

Sep 27 18:19:22 alex-XPS-15-9530 /usr/lib/gdm3/gdm-x-session[4781]: (II) modeset(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher gufw (missing desktop file)
Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher landscape-client-settings (missing desktop file)
Sep 27 18:19:22 alex-XPS-15-9530 gnome-control-c[6754]: Ignoring launcher ubuntuone-installer (missing desktop file)
Sep 27 18:19:22 alex-XPS-15-9530 dbus-daemon[4819]: Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service'
Sep 27 18:19:22 alex-XPS-15-9530 dbus-daemon[4819]: Activation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service not found.
Sep 27 18:20:29 alex-XPS-15-9530 systemd[1]: Starting Cleanup of Temporary Directories...
Sep 27 18:20:29 alex-XPS-15-9530 systemd-tmpfiles[6783]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Sep 27 18:20:29 alex-XPS-15-9530 systemd[1]: Started Cleanup of Temporary Directories.
Sep 27 18:20:41 alex-XPS-15-9530 bluetoothd[6689]: a2dp-sink profile connect failed for 00:18:16:07:03:FD: Protocol not available
---
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: alex 2188 F.... pulseaudio
 /dev/snd/controlC0: alex 2188 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=9c7af056-2269-4b01-9b5c-eeb6e7b3b43a
InstallationDate: Installed on 2016-06-01 (119 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
MachineType: Dell Inc. XPS 15 9530
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro noprompt persistent quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-generic N/A
 linux-backports-modules-4.8.0-17-generic N/A
 linux-firmware 1.161
Tags: yakkety
Uname: Linux 4.8.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip disk lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 01/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

CUPS is the printing subsystem. I do not know exactly where the Bluetooth support belongs to. Moving to the kernel ...

affects: cups (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1628694

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Alex (alex-chapiro) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Alex (alex-chapiro) wrote : CRDA.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : IwConfig.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : JournalErrors.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : Lspci.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : Lsusb.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : ProcEnviron.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : ProcModules.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : PulseList.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : RfKill.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : UdevDb.txt

apport information

Revision history for this message
Alex (alex-chapiro) wrote : WifiSyslog.txt

apport information

Alex (alex-chapiro)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Alex (alex-chapiro) wrote : Re: [Bug 1628694] Re: Ubuntu 16.10 bluetooth doesn't work

Definitely it happened after some upgrade, two-three months before
now. I'm currently running Linux version 4.8.0-17. The bug was in
previous version as well. If I load daily build 30 SEnt 2016, it also
uses kernel 4,8,0-17 generic and it also has this bug. At the same time
content of directory /lib/firware/bcrm is:

bcm4329-fullmac-4.bin
bcm43xx-0.fw
bcm43xx_hdr-0.fw
brcmfmac43143.bin
brcmfmac43143-sdio.bin
brcmfmac43236b.bin
brcmfmac43241b0-sdio.bin
brcmfmac43241b4-sdio.bin
brcmfmac43241b5-sdio.bin
brcmfmac43242a.bin
brcmfmac4329-sdio.bin
brcmfmac4330-sdio.bin
brcmfmac43340-sdio.bin
brcmfmac4334-sdio.bin
brcmfmac4335-sdio.bin
brcmfmac43362-sdio.bin
brcmfmac4339-sdio.bin
brcmfmac43455-sdio.bin
brcmfmac4350c2-pcie.bin
brcmfmac4350-pcie.bin
brcmfmac4354-sdio.bin
brcmfmac43569.bin
brcmfmac4356-pcie.bin
brcmfmac43570-pcie.bin
brcmfmac43602-pcie.ap.bin
brcmfmac43602-pcie.bin
brcmfmac4366b-pcie.bin
brcmfmac4371-pcie.bin

On 2016-10-03 02:52 PM, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> tohttps://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.8 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0]http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

Alex (alex-chapiro)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
D (360-dennis) wrote :

I have the same problem, but i'm on a Dell XPS13-9350 with BCM4350 (installed it myself before the dev edition came out). I have a headset Jabra Evo, that used to work fine in 15.10, stutters on 16.04.1 and does not detect on 16.10. I also have trouble with an other headset, a plantronics voyager legend. It worked fine on 15.10, reconnecting/detection issues in 16.04 and i haven't tried 16.10 yet.

Let me know what I can do to give more information. In the meantime, i'm considering placing back the original intel card to see if that makes a difference.

Revision history for this message
Bob Vincent (pillarsdotnet) wrote :

Same problem with Intel bluetooth on a Lenovo T560. Apport info follows...

Revision history for this message
Bob Vincent (pillarsdotnet) wrote :

Fooey. Apport is also broken:

root@T560:~# apport-collect 1628694
Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 19, in <module>
    from gi.repository import GLib, Wnck, GdkX11, Gdk
  File "/usr/lib/python2.7/dist-packages/gi/importer.py", line 145, in load_module
    importlib.import_module('gi.repository.' + dep.split("-")[0])
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/lib/python2.7/dist-packages/gi/importer.py", line 145, in load_module
    importlib.import_module('gi.repository.' + dep.split("-")[0])
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/lib/python2.7/dist-packages/gi/importer.py", line 145, in load_module
    importlib.import_module('gi.repository.' + dep.split("-")[0])
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/lib/python2.7/dist-packages/gi/importer.py", line 145, in load_module
    importlib.import_module('gi.repository.' + dep.split("-")[0])
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/lib/python2.7/dist-packages/gi/importer.py", line 146, in load_module
    dynamic_module = load_overrides(introspection_module)
  File "/usr/lib/python2.7/dist-packages/gi/overrides/__init__.py", line 125, in load_overrides
    override_mod = importlib.import_module(override_package_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
ImportError: dynamic module does not define init function (initGObject)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.