can't start bluetooth

Bug #1581814 reported by Daniele
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Bluetooth works (Asus Zenbook UX301LA) neither on Ubuntu 16.04 nor Linux Mint 17.3 (both systems updated).
Bluetooth used to work on previous versions of Ubuntu and Mint. The Asus is two year-old and a quick look inside the pc shows no sign of dirt. It doesn't seem possible to remove the wireless card without resorting to wire-cutting + soldering.

the following occurs:
1) with wifi enabled (wifi works perfectly):
a) icon in taskbar is grayed out;
b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth settings>both bluetooth and bluetooth visibility appear as "off" + the message "bluetooth is disabled" appears.

2) with wifi disabled and after re-booting Asus:
a) icon in taskbar lits up;
b) click on icon>can turn on bluetooth + can't turn on visibility>bluetooth settings>bluetooth appears as "on" and bluetooth visibility appear as "off" + the message "bluetooth is disabled" appears.

here are a couple of terminal outputs (if relevant, forgive my total ignorance on the subject):

ubuntu-bug linux
== ApportVersion =================================
2.14.1-0ubuntu3.19

== Architecture =================================
amd64

== CurrentDesktop =================================
X-Cinnamon

== Date =================================
Sat May 14 14:39:57 2016

== Dependencies =================================
adduser 3.113+nmu3ubuntu3
apt-utils 1.0.1ubuntu2.13
base-passwd 3.5.33
busybox-initramfs 1:1.21.0-1ubuntu1
coreutils 8.21-1ubuntu5.4
cpio 2.11+dfsg-1ubuntu1.2
dbus 1.6.18-0ubuntu4.3
debconf 1.5.51ubuntu2
debconf-i18n 1.5.51ubuntu2
debianutils 4.4
:

sudo iw dev wlan0 scan | grep -i "ds parameter set"
[sudo] password for weword:
 DS Parameter set: channel 11
 DS Parameter set: channel 1
 DS Parameter set: channel 1
 DS Parameter set: channel 6
 DS Parameter set: channel 6
 DS Parameter set: channel 6
 DS Parameter set: channel 11
 DS Parameter set: channel 36

cat /var/log/dmesg | grep "firmware version"
[ 1.743848] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x671f07)
[ 3.527075] iwlwifi 0000:02:00.0: loaded firmware version 25.17.12.0 op_mode iwlmvm

additional info: I tried to update the bios - extracted the latest BIOS 207 (if I chose the right one in the first place) - onto flash card but Bios>Advanced>Start EasyFlash can't detect any file on my (FAT32-formatted) flash card.

any idea?
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: weword 1722 F.... pulseaudio
 /dev/snd/controlC1: weword 1722 F.... pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=8e1a6531-0abd-4022-a514-b51bf132748e
InstallationDate: Installed on 2016-05-13 (2 days ago)
InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
Lsusb:
 Bus 001 Device 005: ID 03eb:8a0c Atmel Corp.
 Bus 001 Device 004: ID 1bcf:2987 Sunplus Innovation Technology Inc.
 Bus 001 Device 008: ID 8087:07dc Intel Corp.
 Bus 001 Device 002: ID 8087:8000 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX301LA
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=53898d7a-d497-46ac-9b39-a6730acb2f39 ro quiet splash acpi_osi= vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-32-generic N/A
 linux-backports-modules-3.19.0-32-generic N/A
 linux-firmware 1.127.22
Tags: rosa
Uname: Linux 3.19.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX301LA.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX301LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LA.205:bd11/05/2013:svnASUSTeKCOMPUTERINC.:pnUX301LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX301LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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 1581814

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
Daniele (dcalvani) wrote :

 $ apport-collect 1581814
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=3PxFVP5LZQ8ptd0Xcrqb&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...

Waiting to hear from Launchpad about your decision...

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
dpkg-query: no packages found matching linux
.....

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (1.5 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): V
Traceback (most recent call last):
  File "/usr/bin/apport-cli", line 370, in <module>
    if not app.run_argv():
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv
    return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 569, in run_update_report
    response = self.ui_present_report_details(allowed_to_report)
  File "/usr/bin/apport-cli", line 209, in ui_present_report_details
    self.collect_info()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 967, in collect_info
    if self.report['ProblemType'] == 'Crash':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniele (dcalvani) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected rosa
description: updated
Revision history for this message
Daniele (dcalvani) wrote : BootDmesg.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : CRDA.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : IwConfig.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : Lspci.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : ProcModules.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : PulseList.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : RfKill.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : UdevDb.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : UdevLog.txt

apport information

Revision history for this message
Daniele (dcalvani) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 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.6-yakkety

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Daniele (dcalvani) wrote :

kernel-bug-exists-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniele (dcalvani) wrote :

bluetooth now works on the following kernel

$ dpkg --list | grep linux-image
ii linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP
ii linux-image-extra-3.19.0-32-generic 3.19.0-32.37~14.04.1 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x86 SMP

(Linux Mint Cinnamon 17.03)

Revision history for this message
Daniele (dcalvani) wrote :

forgotten to add that it works following a fresh install of Linux Mint 17.3
and
that it no longer work if I follow the "update manager" instructions to update the system.

i don't know which package in the update causes the problem.

Revision history for this message
Ivan D. Sanders (vandelsand) wrote :

I think the solution to this bug is

systemctl enable bluetooth

You have to enter your password 4-5 times and then reboot. It worked for me. can someone else try it to confirm on Asus laptops with this bug?

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.