Description of problem: The problem is that many users with laptops (it might also affect desktops) have no wifi or bluetooth. The hardware kill switches appear to do nothing (though the state change is happening). Both are softblocked. Running as root: [root@localhost ~]# rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hp-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 2: hp-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 3: hp-gps: GPS Soft blocked: yes Hard blocked: yes Wifi and bluetooth are soft blocked! And there is absolutely no way of turning this on in Mageia except for running one of the commands: [root@localhost ~]# rfkill unblock wifi [root@localhost ~]# rfkill unblock bluetooth [root@localhost ~]# rfkill unblock all Installing NetworkManager does not help. The soft block switch is not accessible in the Control Centre or Network Centre. The user must run these commands as root every time the computer is turned on, as the state is not stored. Version-Release number of selected component (if applicable): How reproducible: 100% for all affected hardward. Steps to Reproduce: 1. Turn laptop on. Possible permanent solution: The idea is from https://bbs.archlinux.org/viewtopic.php?pid=1210751#p1210751. First create a systemd configuration file (which could be in the systemd-units RPM package). As root, edit the new /usr/lib/systemd/system/rfkill-unblock.service file: [root@localhost ~]# gvim /usr/lib/systemd/system/rfkill-unblock.service - Add the text to unblock everything: [Unit] Description=RFKill-Unblock All Devices [Service] Type=oneshot ExecStart=/usr/sbin/rfkill unblock all ExecStop= RemainAfterExit=yes [Install] WantedBy=multi-user.target - Activate: [root@localhost ~]# systemctl enable rfkill-unblock.service ln -s '/usr/lib/systemd/system/rfkill-unblock.service' '/etc/systemd/system/multi-user.target.wants/rfkill-unblock.service' [root@localhost ~]# After this, the wifi and bluetooth will be accessible. The hardware kill switch then appears to be functional again (whereas with the soft block, it appears to be dead). Possibly related bugs: https://bugs.mageia.org/show_bug.cgi?id=1452 https://bugs.mageia.org/show_bug.cgi?id=5015 https://bugs.mageia.org/show_bug.cgi?id=7828 https://bugs.mageia.org/show_bug.cgi?id=8062 https://bugs.mageia.org/show_bug.cgi?id=8930 https://bugs.mageia.org/show_bug.cgi?id=9950 https://bugs.mageia.org/show_bug.cgi?id=10032 https://bugs.mageia.org/show_bug.cgi?id=12544 And many, many more when searching the bug tracker for 'wifi' or 'bluetooth'. Reproducible: Steps to Reproduce:
CC: (none) => true.bugman
It can happends that drakx-net and networkmanager are in conflct resulting this case
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD