This serious issue is dragging to long. People want computers that "just work". If pinpointing the source of the problem is difficult and few resources are available, why not package a workaround that restarts NetworkManager upon resume?
Attached is my workaround. Works nicely. Finally, I have a computer that "just works" and it's not a Mac (well, I have other issues but this one is solved).
Simple move the script under /lib/systemd/system-sleep and ensure it is executable.
This serious issue is dragging to long. People want computers that "just work". If pinpointing the source of the problem is difficult and few resources are available, why not package a workaround that restarts NetworkManager upon resume?
Attached is my workaround. Works nicely. Finally, I have a computer that "just works" and it's not a Mac (well, I have other issues but this one is solved).
Simple move the script under /lib/systemd/ system- sleep and ensure it is executable.