06-28-2017, 06:35 PM
(06-28-2017, 04:48 PM)Luke Wrote: The systemd script I posted DOES solve the issue.
Not so fast Luke! He said the script you posted at the top of the thread didn't fix it for him! :-P So either we have operator error, or a different issue
(06-28-2017, 03:42 PM)falcon15500 Wrote: So I take it that it hasn't been fixed upstream? That's a bummer. Like everyone else I have the issue with my PB but as I use the one access point most of the time, it's more of an aesthetic nuisance.
I can't work out heads of tails of that. I see mention in the bug tracker that it is fixed in the debian jessie repo, but it seems there are too many dependencies to install that newer version cold turkey on xenial 16.04. Someone else says they've done their own fix, but have only provided x86/x64 builds, so no armhf/arm64 debs. I also mostly use just the one access point, so it's just an aesthetic nuisance for me also. That's why I was curious to know if network-manager is doing it's job or not. Namely, if when moving to a different access point, it it still connects, but the GUI applet just isn't updating. i.e. the output of 'nmcli c' saying that network-manager has connected to a pre-configured access point that wasn't in range when the system was put to sleep, without a restart of the service on resume. If it isn't connecting, then it obviously needs refreshing also.
