On Fri, Jun 03, 2022 at 04:00:20PM +0200, 'qtpie' via qubes-users wrote:
So, apparently, this is not a sys-firewall, but a clocksync issue. To root out any causes, I moved the clocksync service to a separate, brand new qube (named sys-clock). And voila: sys-firewall no longer 'crashes' on resume from suspend, now it's sys-clock.

This should probably be filed as an issue:
github.com/QubesOS/qubes-issues

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/YpssUiKTrfhVS/og%40danwin1210.de.

Reply via email to