Description of problem: After setting 'Aeroplane Mode' (Airplane Mode) to 'on', do 'Restart', after which Aeroplane Mode is 'off' (WiFi on), previous status forgotten. Version-Release number of selected component (if applicable): LABEL=Fedora-Live-Dsgn-x86_64-23_B-1 Steps to Reproduce: 1. Boot, switch on Aeroplane Mode (WiFi off); 2. Reboot; 3. Check Aeroplane Mode. Actual results: Aeroplane Mode has been turned off by reboot. Expected results: Previous 'on' state should be remembered. Additional info: Will test 32-bit HW.
NetworkManager has WirelessEnabled property, which can be set. https://developer.gnome.org/NetworkManager/0.9/spec.html#org.freedesktop.NetworkManager $ nmcli radio wifi off disables Wi-Fi and NetworkManager saves the value into /var/lib/NetworkManager/NetworkManager.state so that it is persistent across reboot (NM restart). However, Gnome seems to be using org.gnome.SettingsDaemon.Rfkill for "Airplane Mode". That will not make NM to store the value.
It's systemd's job to save the rfkill status. Please attach the output of "rfkill list" before and after reboot. Which versions of gnome-bluetooth and bluez are installed?
(In reply to Bastien Nocera from comment #2) > It's systemd's job to save the rfkill status. > > Please attach the output of "rfkill list" before and after reboot. Which > versions of gnome-bluetooth and bluez are installed? Additional info: Tried 32-bit version; same problem, this time, with external USB WiFi adapter. Version-Release number of selected component (if applicable): CDLABEL=Fedora-Live-Dsgn-i686-23_B-1 \/ [root@localhost webs]# rfkill list bash: rfkill: command not found... Install package 'rfkill' to provide command 'rfkill'? [N/y] y Airplane Mode 'on': [root@localhost webs]# rfkill list 1: phy1: Wireless LAN Soft blocked: yes Hard blocked: no [root@localhost webs]# Airplane Mode after reboot: [root@localhost webs]# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no [root@localhost webs]# Remove USB adapter: [root@localhost webs]# rfkill list [root@localhost webs]# Replace USB adapter (what?): [root@localhost webs]# rfkill list 1: phy1: Wireless LAN Soft blocked: yes Hard blocked: no [root@localhost webs]# Another terminal: [webs@localhost ~]$ nmcli radio wifi off [webs@localhost ~]$ Airplane Mode after 'Restart': 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no [root@localhost webs]# Remove USB adapter: [root@localhost webs]# rfkill list [root@localhost webs]# Replace USB adapter: [root@localhost webs]# rfkill list 1: phy1: Wireless LAN Soft blocked: yes Hard blocked: no [root@localhost webs]# \/ [webs@localhost ~]$ rpm -qa |grep bluez bluez-cups-5.33-1.fc23.i686 bluez-5.33-1.fc23.i686 bluez-libs-5.33-1.fc23.i686 [webs@localhost ~]$ [webs@localhost ~]$ rpm -qa |grep bluetooth NetworkManager-bluetooth-1.0.6-2.fc23.i686 gnome-bluetooth-libs-3.17.90-2.fc23.i686 pulseaudio-module-bluetooth-7.0-1.fc23.i686 gnome-bluetooth-3.17.90-2.fc23.i686 [webs@localhost ~]$ Will get 64-bit versions on next session.
(In reply to Bastien Nocera from comment #2) > It's systemd's job to save the rfkill status. > > Please attach the output of "rfkill list" before and after reboot. Which > versions of gnome-bluetooth and bluez are installed? 64-bit versions (after 'dnf update'): [nbtt@localhost ~]$ rpm -qa |grep bluez bluez-5.35-1.fc23.x86_64 bluez-cups-5.35-1.fc23.x86_64 bluez-libs-5.35-1.fc23.x86_64 [nbtt@localhost ~]$ rpm -qa |grep bluetooth pulseaudio-module-bluetooth-7.1-1.fc23.x86_64 gnome-bluetooth-libs-3.18.0-1.fc23.x86_64 gnome-bluetooth-3.18.0-1.fc23.x86_64 NetworkManager-bluetooth-1.0.6-8.fc23.x86_64 [nbtt@localhost ~]$
(In reply to Bastien Nocera from comment #2) > It's systemd's job to save the rfkill status. > > Please attach the output of "rfkill list" before and after reboot. Which > versions of gnome-bluetooth and bluez are installed? 64-bit versions (before 'dnf update'): bluez-5.33-1.fc23.x86_64 gnome-bluetooth-1:3.17.90-2.fc23.x86_64 .
The problem is that the device name changes from "phy0" to "phy1". It should have the same predictable name though, which I believe, is applied through udev rules. If the interface name stops changing, I'm pretty sure this will work as expected. Reassigning.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.