[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

2017-11-05 Thread Daniel van Vugt
OK, thanks. This is then a simple enhancement request to reduce excessive logging, per comment #18. ** Summary changed: - Failed to set mode: Blocked through rfkill (0x12) + Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill

[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

2017-11-03 Thread joshas
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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

2017-11-03 Thread Daniel Klafft
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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu.

[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

2017-10-30 Thread joshas
apport information ** Tags added: apport-collected artful wayland-session ** Description changed: 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 +

[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

2017-10-30 Thread Daniel van Vugt
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-

[Touch-packages] [Bug 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)

2017-10-30 Thread Daniel van Vugt
Please also try this command to stop the error message happening: sudo rfkill unblock all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1728385 Title: Failed to set