I’ve encountered an issue similar to #1 after waking up from the suspend state.My only fix for this is to delete the configuration and recreate it with all of the same data. By “break”, I mean that the system won’t even attempt to connect to the network, even though the configuration is correct. Almost every time the fedora-34 template is modified, either by me or via system updates, this breaks my Wi-Fi configuration upon reboot.Regarding the following issues, note that I’ve done virtually nothing to the system beyond installing system updates and tweaking the Firefox settings in the AppVMs and template VMs. The installation completed without any issues that I saw. I downloaded and verified the v4.1.0 ISO (integrity and authenticity), then flashed it with Rufus from Windows 10 in DD mode. I gave up on v4.0.4 and decided to try v4.1.0. However, this ran into the same error I saw before: “qubes-prefs: error: Failed to connect to qubesd service: Connection refused”. When I rebooted, it did correctly take me to the Initial Setup, which the previous installation did not. The installation completed without throwing any obvious errors. When I looked in the Qube manager, the debian-10 template wasn’t there, but there was a “tmp-debian-10” that the system installed, which is odd.īy this point, I had decided that I couldn’t trust this installation, so I reinstalled the OS… After more fiddling, I ran into other issues like the system claiming the Tor browser wasn’t even installed in the whonix-ws disposable VM, which wasn’t true. Then I restarted and was able to log in, but received the message “Domain sys-firewall has halted” and then the OS froze again. Then I rebooted and the OS froze on the Qubes splash screen, so I had to do a force-shutdown. I restarted and attempted the Initial Setup again a couple of times, then ran into error “…can retry configuration by calling ‘sudo qubesctl state.highstate’ in dom0 (you will get detailed state there).” I called this command, and it claimed “Succeeded: 28 (changed=2)” and “Failed: 0”. I manually ran the Initial Setup, but this threw a dom0 error “qubes-prefs: error: Failed to connect to qubesd service: Connection refused”. The installation completed without throwing any obvious errors, but when I restarted, it skipped the Initial Setup step, leaving me nothing but dom0 in the Qube Manager. I let it got for ~7.5 hours before I did a force-shutdown. The installer froze on step “Installing qubes-mgmt-salt-dom0-update.noarch (821/1016)”. The only setting I changed was enabling “Enable system and template updates over the Tor anonymity network using Whonix” because why not?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |