Workaround tested on HP tx2020eo:
Step 1: Unchecking and checking the "Enable wireless" setting in the NM taskbar icon (right click) immediately starts the scan and connection.
Step 2: Requesting the same via the command line through the following works as well:
dbus-send --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.DBus.Properties.Set string:org.freedesktop.NetworkManager string:WirelessEnabled variant:boolean:false dbus-send --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.DBus.Properties.Set string:org.freedesktop.NetworkManager string:WirelessEnabled variant:boolean:true
Step 3: Putting the above two lines in /etc/acpi/resume.d/92-kick-network-manager.sh with appropriate permissions works, starting the wireless connection on resume.
Workaround tested on HP tx2020eo:
Step 1: Unchecking and checking the "Enable wireless" setting in the NM taskbar icon (right click) immediately starts the scan and connection.
Step 2: Requesting the same via the command line through the following works as well:
dbus-send --system --type=method_call --dest= org.freedesktop .NetworkManager /org/freedeskto p/NetworkManage r org.freedesktop .DBus.Propertie s.Set string: org.freedesktop .NetworkManager string: WirelessEnabled variant: boolean: false org.freedesktop .NetworkManager /org/freedeskto p/NetworkManage r org.freedesktop .DBus.Propertie s.Set string: org.freedesktop .NetworkManager string: WirelessEnabled variant: boolean: true
dbus-send --system --type=method_call --dest=
Step 3: Putting the above two lines in /etc/acpi/ resume. d/92-kick- network- manager. sh with appropriate permissions works, starting the wireless connection on resume.