When I freshly installed Qubes 4.3.1, I find that when I try to right-click on Sys-try icon, the dropdown menu only lists “Exit” although I found it’s still working when I tested it on the Tor browser.
But when I reboot the OS, Sys-Whonix does not start up and I have to start it up manually.
Am I the only one having this issue?
Make sure this shows True when you run it in dom0:
qvm-prefs sys-whonix autostart
If it doesn’t, just set it.
I ran the command. It came out as true.
So I rebooted my computer… Nope, I still can’t access the Tor control panel from the taskar.
So I tried it from the start menu… It opened up just fine.
This means sys-whonix should automatically start at boot. Does it?
So I rebooted my computer… Nope, I still can’t access the Tor control panel from the taskar.
So I tried it from the start menu… It opened up just fine.
Might be an in-VM issue?
Try to debug this by looking at logs. That’s what I would do for a start.
If you can’t find the reason, you can re-create sys-whonix using a salt formula. IIRC, there is info how to do this on Whonix’s doc website.
Hi. Sorry for the late reply.
I had been trying to get to the bottom of the issue.
Again, the Tor Control Panel works fine and sys-whonix connects to Tor alright.
It’s only when I open sys-whonix’s sdwdate-gui in the app menu does it finally show up when I right-click on the icon (the Time synchronization monitor) in the taskbar.
Keep in mind though, that I ran @abdullah’s hardening script which changed default-dvm’s template (and thus sys-whonix’s) to kicksecure-18 which complicated things when I tried to debug it.
It’s when I changed sys-whonix’s boot mode to SYSMAINT, apparently everything got fixed. After rebooting, I still have to manually open its sdwdate-gui to get it to show up though but otherwise it seems to be working fine now.
I switched sys-whonix’s boot mode back to default and rebooted the OS.
I still have to manually open sdwdate-gui but its still running okay, it seems.