Dear maintainer,

when the computer resumes after an extended resume, Tor does not notice
that. That leads to open Tor circuits being invalid.

The bug was reported a few years ago. Original bug report upstream at Tor:
https://gitlab.torproject.org/tpo/core/tor/-/issues/25456

But it was never done because Tor's systemd unit was deprecated:
https://gitlab.torproject.org/tpo/core/tor/-/issues/30797

Another user reported the same issue but noted that SIGHUP isn't a
reliable solution either.
https://gitlab.torproject.org/tpo/core/tor/-/issues/40200

Therefore Tor's systemd service should restart Tor on resume/thaw after
sleep/hibernate to fix the connectivity issue.

Cheers,
Patrick

4 year old version of tor. As far as I can tell, the version of tor in
debian oldstable/stable/unstable recognize it when clock changes due to
suspend/resume and deal with it appropriately.

If you can reproduce the problem in a supported version of tor, please
open a new bugreport.

Closing.