Don't pretend tor has bootstrapped when tor@default.service failed to start
Without this commit, this could — and would! — happen:
-
tor@default.service
fails to start enough times for systemd to give up (fixed in !584 (merged)) -
tails-wait-until-tor-has-bootstrapped.service
correctly fails thanks toBindsTo=tor@default.service
-
tails-tor-has-bootstrapped-flag-file.service
incorrectly starts. It tells the rest of the system, most notably Tor Connection and the Onion status icon in the top bar, that Tor is ready, while we still have "DisableNetwork 1" in torrc.
Closes #18532 (closed)
Edited by intrigeri