NM does not memorize network activation state on suspend/resume or restart
Bug #387345 reported by
pittipatti
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
NetworkManager |
Fix Released
|
Medium
|
|||
network-manager (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: network-manager
After resuming from suspend (or restarting) I would expect the system to be in the same networking state as as before the suspend.
In particular when networking was disabled before suspending, I would expect it to still be disabled after resuming.
But, networking allways gets enabled after resuming or restarting the system.
Related branches
CVE References
summary: |
- NM does not memorize network state on suspend/resume or restart + NM does not memorize network activation state on suspend/resume or + restart |
Changed in network-manager: | |
status: | Unknown → Confirmed |
Changed in linux: | |
status: | Unknown → Fix Released |
Changed in network-manager (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in network-manager: | |
status: | Confirmed → In Progress |
Changed in network-manager: | |
status: | In Progress → Fix Released |
tags: | added: lucid |
Changed in network-manager: | |
importance: | Unknown → Medium |
Changed in linux: | |
importance: | Unknown → Medium |
To post a comment you must log in.
i think restarting is ok to forget the state. howver, suspend/resume sounds reasonable.