Disabling FlightMode after a reboot can result in Wi-Fi incorrectly being enabled
Bug #1354716 reported by
Tony Espy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
urfkill (Ubuntu) |
Fix Released
|
Medium
|
Tony Espy |
Bug Description
If Wi-Fi is disabled, Flight-Mode enabled, the device rebooted and Flight disabled, Wi-Fi will incorrectly be enabled.
Reproduced on mako running image #u172.
Changed in urfkill (Ubuntu): | |
importance: | Undecided → Medium |
Changed in urfkill (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Tony Espy (awe) |
Changed in urfkill (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package urfkill - 0.6.0~20141007. 235123. f908aff. 1-0ubuntu1
--------------- 20141007. 235123. f908aff. 1-0ubuntu1) utopic; urgency=medium
urfkill (0.6.0~
* New release snapshot: patches/ ignore_ input_monitor_ startup. patch: dropped, included scripts/ enumerate: handle the new hybris device type.
- Asynchronous support for rfkill operations. (LP: #1321627, #1339794)
- Improvements to state persistence. (LP: #1354716)
- Support for devices driven by libhybris rather than rfkill.
* debian/
upstream.
* debian/control:
- bump Build-Depends on libglib2.0-dev to >= 2.36 for GTask.
- add a Build-Depends on libhybris-dev for hybris-driven devices support.
- bump Standards-Version to 3.9.5.
* debian/
* debian/rules: remove SysV init startup links.
-- Mathieu Trudel-Lapierre <email address hidden> Tue, 07 Oct 2014 23:53:07 -0400