http://bugzilla.opensuse.org/show_bug.cgi?id=977944 http://bugzilla.opensuse.org/show_bug.cgi?id=977944#c8 Stakanov Schufter <stakanov@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 42.1 |Leap 42.2 Summary|After suspend to ram or |After setting up a wlan |suspend to disk Privoxy is |connection privoxy goes |not functional with WLAN or |into failed state |LAN and does not behave as | |expected. | Flags|needinfo?(mseben@gmail.com) | --- Comment #8 from Stakanov Schufter <stakanov@freenet.de> --- 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? -- You are receiving this mail because: You are on the CC list for the bug.