Tom H writes:
Does privoxy start properly if you disable NM and its wait-online
and use systemd-networkd and its wait-online unit?
Does privoxy start properly if you disable NM's wait-online unit and
use a custom wait-online unit that waits until
"/sys/class/net/<IF>/carrier" is "1"?
privoxy starts properly most of the time right now, already.
But I really don't understand why so much research is needed for this issue,
by disabling random things, and then trying other random things. Either
NetworkManager-wait-online actually waits until the network interfaces have
their IP address set, or it doesn't. If it's supposed to do it, then it
should be possible to isolate the issue without turning it off completely
and switching to a completely different network configuration
infrastructure. If it's not supposed to do it, then what exactly is it
supposed to be doing, anyway?