Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill (0x12)"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Triaged
|
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
PackageArchitec
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
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.
dmi.board.name: 20GJ001HMH
dmi.board.vendor: LENOVO
dmi.board.version: S
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad S2
dmi.product.name: 20GJ001HMH
dmi.product.
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
Changed in bluez (Ubuntu): | |
status: | Expired → New |
status: | New → Confirmed |
tags: |
added: bionic removed: artful |
Changed in bluez (Ubuntu): | |
status: | Confirmed → Triaged |
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/ReportingBu gs.