bluetooth will not enable stays blocked

[Daniel Evans]

Since installation of 14.04.1 I've been trying to get bluetooth working. Under preferences bluetooth says it's disabled. So I did $rfkill list all, and that showed me that asus bluetooth is soft blocked. I did an $rfkill unblock all, and nothing. I have tried everything listed here: http://askubuntu.com/questions/521190/bluetooth-disabled-asus-g750jm and the person answering my questions suggested I report it as a bug because I'm out of options.

I'm running a ROG ASUS G750JM it's a fairly new gaming laptop, the modem installation went fine through the install process of ubuntu. But bluetooth hasn't worked yet.

I'm not sure what package it is it's probably bluez and it's up to date.
---
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-09-06 (9 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
InterestingModules: rfcomm bnep bluetooth
MachineType: ASUSTeK COMPUTER INC. G750JM
NonfreeKernelModules: wl
Package: bluez 4.101-0ubuntu13
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=d4bccb16-54c7-4324-a7b8-7ed0f79c9183 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Tags: trusty third-party-packages
Uname: Linux 3.13.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G750JM.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G750JM
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.:bvrG750JM.207:bd07/17/2014:svnASUSTeKCOMPUTERINC.:pnG750JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G750JM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:

[Daniel Evans (gleamingjewel)]

After looking into it further this is probably not related to the bluez package because my device isn't even listed under lspci

[Lucy Llewellyn (lucyllewy)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. I believe you were right to file this under bluez, so I've reassigned it back there. While waiting for someone to take a look, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1366854

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

apport information

[Daniel Evans (gleamingjewel)]

Since upgrading to 14.10 bluetooth works when I do $rfkill unblock all, so I added that to be performed at launch.

[Daniel van Vugt (vanvugt)]

Ubuntu 14.04 reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

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 and change the bug status to Confirmed.