rfkill state is not restored on reboot

Bug #1548057 reported by Adam Groszer on 2016-02-21
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Undecided
Unassigned

Bug Description

1. Disable bluetooth via applet.
2. Reboot.
3. Login.
4. Observe bluetooth is re-enabled!

For fun having

rfkill block bluetooth

in rc.local does not work either

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: rfkill 0.5-1ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Feb 21 13:37:39 2016
InstallationDate: Installed on 2013-05-17 (1010 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
SourcePackage: rfkill
UpgradeStatus: No upgrade log present (probably fresh install)

Adam Groszer (agroszer) wrote :
Steve Langasek (vorlon) wrote :

This is now handled by the systemd package (/lib/systemd/systemd-rfkill; /lib/systemd/system/rfkill.service). And yes, it is buggy from what I can see.

affects: rfkill (Ubuntu) → systemd (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers