This bug was fixed in the package urfkill -
0.6.0~20141007.235123.f908aff.1-0ubuntu1
---------------
urfkill (0.6.0~20141007.235123.f908aff.1-0ubuntu1) utopic; urgency=medium
* New release snapshot:
- Asynchronous support for rfkill operations. (LP: #1321627, #1339794)
- Improvements to state persistence. (LP: #1354716)
- Support for devices driven by libhybris rather than rfkill.
* debian/patches/ignore_input_monitor_startup.patch: dropped, included
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/scripts/enumerate: handle the new hybris device type.
* debian/rules: remove SysV init startup links.
-- Mathieu Trudel-Lapierre <[email protected]> Tue, 07 Oct 2014 23:53:07
-0400
** Changed in: urfkill (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354716
Title:
Disabling FlightMode after a reboot can result in Wi-Fi incorrectly
being enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1354716/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
