Seems to me that if NM stalls due to a race condition, then restarting NM
*is* a workaround, so yes, adding additional scripts to systemd is a
solution, but not the "answer".
derek
On Fri, Feb 3, 2017 at 1:11 AM, Tony Espy <1585...@bugs.launchpad.net>
wrote:
> @Kevin
>
> NetworkManager already h
You're kidding? "no longer affects:network-manager"
It certainly did as recently as yesterday!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863
Title:
@JaSauders I think the downside is that restarting NetworkManager, on a
system that doesn't have any problem with network connections after a
suspend event (and that surely must be most systems, or this would be
fixed already) will result in a much slower reconnection to the network.
--
You recei
btw, merely restarting Network Manager never worked for me. I have to
remove iwlwifi and reload it.
derek
On Thu, Nov 17, 2016 at 2:18 PM, Derek Broughton
wrote:
> We used to have this. I'm sure, a decade ago, I could actually tell
> whatever was managing the hibernate/suspend, in the gui, to r
We used to have this. I'm sure, a decade ago, I could actually tell
whatever was managing the hibernate/suspend, in the gui, to remove certain
kernel modules on suspend and load them on resume. Now we're right back to
needing it.
derek
On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon wrote:
> This
You can try having the script do "modprobe -r" and "modprobe" on your wifi
module. That should always work, but seemed like overkill in my case. In
any case, these are workarounds, not fixes.
On 4 Aug 2016 6:01 a.m., "Aleve Sicofante" wrote:
> @auspex: Your
I finally worked around my problem by adding a script in /lib/systemd
/system-sleep/:
$ cat /lib/systemd/system-sleep/12_wifi
#!/bin/bash
case $1 in
"post")
# disable/enable wifi
rfkill block wifi; rfkill unblock wifi
logger "reenabled wifi"
;;
because restarting network-manager from sleep.d isn't even a workaround,
let alone a fix. With that, my network successfully reconnects just
about as often as if there is nothing in sleep.d.
Which, apparently, would be because /etc/pm/sleep.d is never invoked.
--
You received this bug notifica
Please don't suggest installing non-standard packages as a "fix" for
broken packages in the default setup. Yeah, Network-manager is a pain
and always has been, but until the distros choose to focus on Wicd
rather than network-manager, NM is the tool that HAS to work to keep
interest in Linux up.
-
What would have fixed it? Given that there are all kinds of things that
have worked for some, and not for others, unless we know a specific
change that should fix the behaviour, I'd say there's still a bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
10 matches
Mail list logo
