Comment # 8 on bug 977944 from Stakanov Schufter

This bug is present also in Leap 42.2 and 42.1 without suspend to RAM. 
What happens (or what seems to happen is): 

Privoxy service starts. When activating the WLAN connection via Networkmanager
in journalctl you find: privoxy entered in failed state. 
Once WLAN is working, if you restart privoxy in systemd, it will work the whole
session for all users on that system correctly. 

There is no error message when opening the browser, only that the page do not
load (from privoxy). This can be very irritating to users and leaves privoxy if
run as a daemon useless. 

The only further note you find in journalctl is the mention: you have modified
/etc/resolve.conf leaving it untouched. 
As I did not modify anything, this seems to be an issue with how the wlan
session is set up by network manager? Maybe this could be the issue of privoxy
going into failed state?