First, sorry for my english.
I’m currently on R4.3.0 and since the last update, I have an issue with the feature “Start qube automatically on boot”.
Issue : After a shutdown, at startup sys-net automatically start, followed by sys-firewall in chain reaction.
But both qubes are disabled, with sys-whonix too (it won’t start this service).
And of course, I checked all my qubes, but none of them have “Start qube automatically on boot” activated linked with sys services. No scripts with autostart or systemd service either.
Only dom0 and sys-usb should start automatically as it has always been for my case.
Is it possible to see how sys-net starts, or is it a bug from the latest update ?
The dumb question : I have a disposable qube launching at every start up, which I can only see in the dropdown menu by clicking on “Qubes Domains”, it’s greyed out and there’s a console log (internal qube). Is this normal? Is it just a harmless log?
This shouldn’t happen. To test, add qubes.skip_autostart to grub temporarily with e at boot up. There was an update in kernel version that seems to be causing issues with sys-net and sys-usb… perhaps related. You could also try loading the older kernel at grub at see if that respects autostart settings
It is the default. A preloaded disp. If you go to global settings and uncheck the disposable box then it wont happen.
When any qube starts up that depends on the network (“depends on” in this case means it has a net qube set in its config), it will cause the network qube to start up as well. Could it be this is what’s happening when the disposable qube starts up?
