Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wpa_supplicant stops working after suspend with debian-11 #7185

Open
mtdcr opened this issue Jan 7, 2022 · 6 comments
Open

wpa_supplicant stops working after suspend with debian-11 #7185

mtdcr opened this issue Jan 7, 2022 · 6 comments
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: networking hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@mtdcr
Copy link

mtdcr commented Jan 7, 2022

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 mtdcr added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Jan 7, 2022
@unman
Copy link
Member

unman commented Jan 8, 2022 via email

@andrewdavidwong andrewdavidwong added C: networking hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Jan 8, 2022
@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Jan 8, 2022
@mtdcr
Copy link
Author

mtdcr commented Jan 15, 2022

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.

@Warthog-Capital
Copy link

Warthog-Capital commented Aug 5, 2022

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

@andrewdavidwong
Copy link
Member

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.

@unman
Copy link
Member

unman commented Aug 6, 2022 via email

@mtdcr
Copy link
Author

mtdcr commented Aug 6, 2022 via email

@andrewdavidwong andrewdavidwong added the affects-4.1 This issue affects Qubes OS 4.1. label Aug 8, 2023
@andrewdavidwong andrewdavidwong removed this from the Release 4.1 updates milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: networking hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

4 participants