On 11/17/2017 06:12 AM, Elias Mårtenson wrote:
On 17 November 2017 at 19:08, Unman <[email protected]
<mailto:[email protected]>> wrote:
You havent said which version if Qubes you are running.
in 3.2 the qubes-netvm service may be responsible. You could try
changing the default netvm, or temporarily disabling the
qubes-netvm.service and see if that changes behaviour.
Oops. Sorry about that. It's 4.0rc2.
I was able to prevent sys-net and sys-firewall auto-start in rc2 by
simply disabling 'Start VM automatically at boot' in settings. The only
other difference is that my default netvm is set to 'VPN' but I wouldn't
expect that to matter.
--
Chris Laprise, [email protected]
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/a4d0c800-6598-89f1-07c8-4ec6e86e1755%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
