I'm just wondering if I'm alone in this. NetworkManager just bugs out a lot. For example, just now when this laptop came out of standby, obviously (perhaps) the wifi had been lost. But it wouldn't reconnect. It just failed. It only worked after I did: service NetworkManager restart. Then it connected automatically. Sometimes when I close my VPN (configured via NM) it won't start up again. I have to go to a shell and run it manually and I don't know why, but NM will just immediately 'return' after clicking my VPN connection's "connect". Perhaps that can be fixed with "service NetworkManager restart" also. The way my system is set up there should really be no flaws. The wifi creates an SSH tunnel, when the wifi goes down the tunnel is killed. The tunnel is there for the VPN, which I create manually from the NM-applet in KDE. When the VPN goes down the tunnel is not closed, it doesn't need to. If the tunnel closes unexpectedly I'm in a bit more trouble, I have to first check whether the tunnel is still live (I do it with tunnel status) and after that I might need to check the connection to the tunnel host, I haven't automated that yet. But closing and reopening wifi also does this. NetworkManager interferes with VPNs it does not set up itself, but it is no great interference, I just cannot delete the default route of the default wifi connection. Troublesome, but no deal breaker at this point because the new openvpn route supersedes it. Troublesome though that NM think it's so important. Anyone else experience these issues? I have had before in another KDE distro as well. I was trying to create my own "NM" suite with scripts but obviously I don't know enough about KDE to create my own applet. And it requires a lot of work to get any sort of roaming support (logging onto different networks). It just seems NM's internal state often goes corrupt. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org