Comment 44 for bug 1585863

I'm surprised this is still a thing. I added the common systemd "restart network-manager on resume" script most folks with this issue have used. I added it quite a while ago. My system has been working consistently since then without issue... to the point I actually forgot that this bug existed.

I understand the burning desire to fix the problem at hand, but months (soon to be a year) later, this issue still exists. I don't see the trade-off/downsides/consequences with this work-around being applied. If a downside does exist, I haven't seen it, but what I have seen is the benefit of it being in place as it circumvents this issue entirely.

Sorry - I just don't see the point of this bug trailing on longer and longer while users unaware of the "restart network-manager on resume" fix continue to deal with the headache, while on the other hand, had that work-around been issued, folks wouldn't be as angry about this issue as they clearly are.