Gfilui

I have an HP Spectre x360 convertible laptop and I'm running Ubuntu 18.04. Every time I turn the screen sideways or in tablet mode and back, 'Airplane Mode' is activated. In fact, when I boot up and login, I have to manually turn off 'Airplane Mode' and turn wifi back on. I don't want to disable the gnome rfkill plugin like so: 'gsettings set org.gnome.settings-daemon.plugins.rfkill active false' because then I can no longer use bluetooth. Also, for some godforsaken reason, even when I DO disable the plugin, the gnome shell turns on 'Airplane Mode' anyway, which means that I have to go turn wifi back on EVERY time I log in. This is so annoying, I really liked where 18.04 was going but this is seriously breaking the whole gnome shell experience.

In the gnome shell, "Airplane Mode" is automatically activated on boot for many HP laptops, when the screen is tilted sideways, or when the lid is opened/closed. The following is a fix for HP laptops running Linux and using the gnome shell. Keycode 240 is defined as KEY_UNKNOWN (a kind of no-op key) in /usr/include/linux/input-event-codes.h. Also your syslog will no longer prompt you to define the HP e057 and e058 codes, which can be remarkably annoying.

First is a fix using a classic SysV init script, placed in the init.d directory and symlinked accordingly (Basically, we want it to run regardless of runlevel on anything except halt (0) or reboot (6)). Second is a systemd service that is far more reliable and perhaps present with recent systemd changes, which also happens to work on Fedora 28 and other distribution platforms. On Fedora in particular, you will find an almost complete absence of scripts in the /etc/init.d directory, along with a little README detailing the transition from SysV to systemd. The first method will work, but the second method is much more "future friendly" especially considering where Ubuntu is heading, and will also work in a slightly less...annoying way. Systemd init scripts are actually quite handy, and fully implemented and used frequently in Ubuntu 18.04.

Old SysV method:

$ sudo sh -c 'printf "#!/bin/shn/usr/bin/setkeycodes e057 240 e058 240n" > /etc/init.d/hp-keycodes'
$ sudo chmod +x /etc/init.d/hp-keycodes
$ sudo ln -s /etc/init.d/hp-keycodes /etc/rc1.d/K01hp-keycodes
$ sudo ln -s /etc/init.d/hp-keycodes /etc/rc2.d/S01hp-keycodes
$ sudo ln -s /etc/init.d/hp-keycodes /etc/rc3.d/S01hp-keycodes
$ sudo ln -s /etc/init.d/hp-keycodes /etc/rc4.d/S01hp-keycodes
$ sudo ln -s /etc/init.d/hp-keycodes /etc/rc5.d/S01hp-keycodes
$ sudo reboot

New Recommended Systemd Method:

$ sudo nano /etc/systemd/system/hp-keycodes.service

Paste the following lines or type them into the file:

[Unit]
Description=HP setkeycodes fix

[Service]
Type=oneshot
Restart=no
RemainAfterExit=no
ExecStart=/usr/bin/setkeycodes e057 240 e058 240

[Install]
WantedBy=rescue.target
WantedBy=multi-user.target
WantedBy=graphical.target

Save and confirm the filename with ctrl-x, y.

$ sudo systemctl daemon-reload
$ sudo systemctl enable hp-keycodes.service
$ sudo reboot

And that's it, no more annoying weird stuff when you tilt your screen or close/open the laptop lid!

I face the very same problem with 17.10 on my HP Spectre x360.
In fact, I face both Nicholas and Pierre-Antoine problems:

• Airplane mode activated every time I login or flip to tablet mode;


• Fn+F12 (Toggle Airplane Mode key) is no longer working.

To quickly toggle the wifi, I made a small script:

## Content of ~/scripts/wifi_toggle : ##
 #!/bin/bash
 str=`export LANGUAGE=en_GB ; nmcli r wifi`
 [ "$str" == "enabled" ] && nmcli r wifi off
 [ "$str" == "disabled" ] && nmcli r wifi on

I rarely use bluetooth, so it only handles wifi, but you can modify it easily to handle both bluetooth and wifi.

All this is a clear regression from 17.04 where everything worked flawlessly. I tried the 18.04 beta but it's the same situation than with 17.10.

Nicholas, Pierre-Antoine, I fill like filling two bug reports on these issues (on report per issue). Do you think you could had a comment in these reports whenever I'm done reporting? This would help confirming the bug status (more than one user affected).

Cheers