qubes-issues icon indicating copy to clipboard operation
qubes-issues copied to clipboard

wpa_supplicant stops working after suspend with debian-11

Open mtdcr opened this issue 3 years ago • 6 comments

How to file a helpful issue

Qubes OS release

  • 4.0.4
  • 4.1.0-rc3

Brief summary

Every time my machine wakes up from suspend, the wireless connection is broken. Selecting a different network from nm-applet does not help. I need to restart wpa_supplicant manually to fix it.

Steps to reproduce

  • Install Qubes OS on ThinkPad T490 with Intel Wireless-AC 9560
  • Use debian-11 for sys-net
  • Install firmware-iwlwifi
  • Connect to a wireless network
  • Enter suspend
  • Exit suspend

Expected behavior

Network connection gets restored.

Actual behavior

Network connection does not get restored.

mtdcr avatar Jan 07 '22 21:01 mtdcr

Whenever this sort of issue comes up, (and it does - see #6570, #5956, #3008) my thought is the same - I don't WANT my machine to start spewing network data when it wakes from suspend. I'm (probably) in a minority.

unman avatar Jan 08 '22 15:01 unman

Whenever this sort of issue comes up, (and it does - see #6570, #5956, #3008) my thought is the same - I don't WANT my machine to start spewing network data when it wakes from suspend. I'm (probably) in a minority.

While I understand your point, I want to make clear that this bug is not about personal preferences, but about software remaining in a disfunctional state after returning from suspend. Just to avoid confusion.

mtdcr avatar Jan 15 '22 12:01 mtdcr

This also happens to me. Wifi does not reconnect after resume from suspend.

Qubes OS release

4.1.1

Brief summary

On a fresh Qubes 4.1.1 installation, my Wifi connection does not come back after I suspend my laptop, and then start it again.

Solutions to make Wifi work again:

  • opening a terminal in sys-net and running sudo systemctl restart wpa_supplicant
  • restarting sys-net, by shutting down all other VMs that recursively depend on it, first
  • restarting Qubes OS

My laptop is Thinkpad T440P with Intel network card (iwlwifi). The template is debian-11. Fully updated, but the issue already happens right after the first start of Qubes OS.

Steps to reproduce

  1. Install Qubes 4.1.1
  2. Connect to wireless LAN
  3. Suspend laptop by closing it, or suspending via the XFCE panel menu,
  4. Resume laptop by opening it or pressing the start button
  5. Unlock the screen

Expected behavior

Wifi should reconnect automatically.

Actual behavior

The NetworkManager icon keeps spinning. Occasionally, a message toast pops up which says that "The network connection has been disconnected". After a few tries, it stops trying and my Wifi remains disconnected.

Some debug output from sys-net:

Possibly related issues

  • https://github.com/QubesOS/qubes-issues/issues/6570
    • Seems to be the same problem but with iwd
  • https://github.com/QubesOS/qubes-issues/issues/3008
    • Qubes 3.2
  • https://github.com/QubesOS/qubes-issues/issues/6587
    • This also happens to me, still with Qubes 4.1. Each network will end up being configured two times in NetworkManager, one for wls6 and one for wls7

Warthog-Capital avatar Aug 05 '22 13:08 Warthog-Capital

restarting sys-net, by shutting down all other VMs that recursively depend on it, first

Just FYI, you don't have to shut down all dependent VMs. You can instead just set sys-firewall's NetVM to none, restart sys-net, then set sys-firewall's NetVM back to sys-net again.

andrewdavidwong avatar Aug 05 '22 16:08 andrewdavidwong

Sometimes, (if restart is absolutely necessary), qvm-kill sys-net && sleep 5 && qvm-start sys-net will do the the job. I have that saved.

unman avatar Aug 06 '22 10:08 unman

FWIW, here's what I ended up with:

$ cat /etc/qubes/suspend-post.d/wpa-supplicant.sh 
#!/bin/sh
if systemctl -q is-active wpa_supplicant.service; then
	systemctl restart wpa_supplicant.service
fi

mtdcr avatar Aug 06 '22 10:08 mtdcr