Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill (0x12)"

Bug #1728385 reported by joshas on 2017-10-29
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Wishlist
Unassigned

Bug Description

Ubuntu 17.10, bluetooth disabled, get error in Logs:
bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
---
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2017-10-24 (6 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20GJ001HMH
Package: bluez 5.46-0ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Tags: artful wayland-session
Uname: Linux 4.13.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/13/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R0CET26W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20GJ001HMH
dmi.board.vendor: LENOVO
dmi.board.version: S
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad S2
dmi.product.name: 20GJ001HMH
dmi.product.version: ThinkPad S2
dmi.sys.vendor: LENOVO
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: E4:B3:18:52:20:69 ACL MTU: 1021:4 SCO MTU: 96:6
  DOWN
  RX bytes:14933 acl:0 sco:0 events:2414 errors:0
  TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1728385

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in bluez (Ubuntu):
status: New → Incomplete
Daniel van Vugt (vanvugt) wrote :

Please also try this command to stop the error message happening:

  sudo rfkill unblock all

apport information

tags: added: apport-collected artful wayland-session
description: updated

apport information

apport information

joshas (joshas) wrote : Lspci.txt

apport information

joshas (joshas) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

joshas (joshas) wrote : UdevDb.txt

apport information

joshas (joshas) wrote : getfacl.txt

apport information

joshas (joshas) wrote : rfkill.txt

apport information

joshas (joshas) wrote : syslog.txt

apport information

I had the same issue on a Lenovo laptop. The command

 sudo rfkill unblock all

mentioned by @vanvugt solved the issue for me.

Linux 4.13.0-16-generic

joshas (joshas) wrote :

Mentioned "rfkill unblock all" command actually enables bluetooth, which I'd like to keep disabled.
bluetoothd should check if device is blocked and do not try setting mode for such devices.

Daniel van Vugt (vanvugt) wrote :

OK, thanks. This is then a simple enhancement request to reduce excessive logging, per comment #18.

summary: - Failed to set mode: Blocked through rfkill (0x12)
+ Reduce/hide excessive logging when Bluetooth is intentionally disabled:
+ "Failed to set mode: Blocked through rfkill (0x12)"
Changed in bluez (Ubuntu):
importance: Undecided → Wishlist
status: Incomplete → Triaged
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

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.

Changed in bluez (Ubuntu):
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
joshas (joshas) wrote :

Issue still exists in Ubuntu 18.04.1 LTS

Changed in bluez (Ubuntu):
status: Expired → New
status: New → Confirmed
tags: added: bionic
removed: artful
Changed in bluez (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers