Hi @cascagrossa, just to clarify: my impression is that in order to
trigger the bug you'll need to suspend somewhere where the WLAN network
you want to connect to at resume time isn't available as it's the scan
aspect of things that appears to be inhibited. This is evidenced by the
fact that he
Also further to #60, I have put the following in mine (Thinkpad X1
Carbon 3) and it does indeed seem to fix the problem so far - been
testing over a few days:
/lib/systemd/system-sleep/wpasupplicant:
post) (sleep 3 ; /sbin/wpa_cli resume) & ;;
16.04.1 fresh install, kernel 4.4.0-59;
Fresh 16.04.1 install on ThinkPad X1 carbon 3 with stock Intel 7265
(802.11abgn) WiFi here; laptop also has a Sierra Wireless EM7345 4G LTE
WWAN integrate USB module.
Typical scenario: I use the WWAN when out and about, suspend the laptop,
come back to office and expect the laptop to re-connect
Public bug reported:
On a number of VMs using Xenial daily builds 20160330 and 20160403, out
of the box (just after booting for the first time), the following
appears in dmesg at boot time:
systemd[1]: systemd-modules-load.service: Main process exited, code=exited,
status=1/FAILURE
systemd[1]:
4 matches
Mail list logo
