Canonical System Image

Bluetooth state reverts to last full shutdown on every reboot

Bug #1521671 reported by Michael Zanetti
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
Medium
Unassigned
Canonical System Image backlog
urfkill (Ubuntu)
Triaged
Critical
Unassigned

Bug Description

Each reboot restores the state when the device was last shut down (not rebooted).

* Turn Bluetooth on
* shut down the device
* turn device back on
* now turn Bluetooth off
* reboot the device
=> Bluetooth is back on
expected: Bluetooth is off

or:

* Turn Bluetooth off
* shut down the device
* turn device back on
* now turn Bluetooth on
* reboot the device
=> Bluetooth is off
expected: Bluetooth is on

$ system-image-cli -i
current build number: 343
device name: krillin
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2015-12-01 15:58:38
version version: 343
version ubuntu: 20151201
version device: 20151028-869191d
version custom: 20151201

phablet@ubuntu-phablet:~$ rfkill list
0: hci0: Bluetooth
        Soft blocked: yes
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

phablet@ubuntu-phablet:~$ bluetoothctl
[NEW] Controller B8:64:91:48:2A:AA Aquaris E4.5 Ubuntu Edition [default]
[NEW] Device 90:03:B7:B9:F0:68 BMW 26911
[NEW] Device B0:B4:48:89:26:F5 Pebble Time 26F5
[bluetooth]# show
Controller B8:64:91:48:2A:AA
        Name: Aquaris E4.5 Ubuntu Edition
        Alias: Aquaris E4.5 Ubuntu Edition
        Class: 0x000000
        Powered: no
        Discoverable: no
        Pairable: yes
        UUIDs:
          Headset AG (00001112-0000-1000-8000-00805f9b34fb)
          Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
          A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
          SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
          Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
          PnP Information (00001200-0000-1000-8000-00805f9b34fb)
          A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
          Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
          Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
          Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
          Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
          Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0523
        Discovering: no

See original description
Michael Zanetti (mzanetti)
description: updated
description: updated
Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
assignee: nobody → John McAleely (john.mcaleely)
importance: Undecided → Critical
milestone: none → ww02-2016
status: New → Confirmed
Michael Zanetti (mzanetti)
description: updated
Revision history for this message
Michael Zanetti (mzanetti) wrote :

Some logs as requested by Simon Fels:

I did turn Bluetooth on. Then rebooted. Bluetooth was off. I waited for a couple of minutes then turned bluetooth on manually through the indicator.

syslog: http://paste.ubuntu.com/13621752/
rfkill saved-states: http://paste.ubuntu.com/13621760/
rfkill list: http://paste.ubuntu.com/13621765/

Revision history for this message
Simon Fels (morphis) wrote :

I went through the logs and it looks like urfkill is not persisting the change rfkill state for Bluetooth.

Changed in urfkill (Ubuntu):
importance: Undecided → Critical
status: New → Triaged
Simon Fels (morphis)
tags: added: bluetooth-ota9 bluez5
Revision history for this message
Michael Zanetti (mzanetti) wrote :

Found some more info:

The behavior seems to be that each reboot restores the state when the device was last shut down (not rebooted). More complete steps how to reproduce:

* Turn Bluetooth on
* shut down the device
* turn device back on
* now turn Bluetooth off
* reboot the device
=> Bluetooth is back on
expected: Bluetooth is off

or:

* Turn Bluetooth off
* shut down the device
* turn device back on
* now turn Bluetooth on
* reboot the device
=> Bluetooth is off
expected: Bluetooth is on

Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
milestone: ww02-2016 → ww08-2016
Pat McGowan (pat-mcgowan)
tags: added: bluetooth
removed: bluetooth-ota9
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Wit the steps in comment #3, the first time it worked properly, the second time it did not. Possibly a race on suspend.

Changed in canonical-devices-system-image:
importance: Critical → Medium
Simon Fels (morphis)
tags: added: bluetooth-ota10
John McAleely (john.mcaleely)
Changed in canonical-devices-system-image:
milestone: ww08-2016 → backlog
Pat McGowan (pat-mcgowan)
description: updated
summary: - Bluetooth is turned off on every reboot
+ Bluetooth state reverts to last full shutdown on every reboot
John McAleely (john.mcaleely)
Changed in canonical-devices-system-image:
assignee: John McAleely (john.mcaleely) → nobody
Revision history for this message
knut (mr-knut) wrote :

On my system the state of bluetooth is always on after reboot. The previous state is not restored.

dpkg:
rfkill 0.5-1ubuntu3
systemd 229-4ubuntu17

Then, I noticed in dmesg log:
upstart: rfkill-restore main process (972) terminated with status 1

call systemd-rfkill like in /etc/init/rfkill-restore.conf:

/lib/systemd/systemd-rfkill load rfkill1
This program requires no arguments.

I think the rfkill-restore.conf and rfkill-store.conf have to be updated to the command line syntax of systemd-rfkill.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.