Sadly, my last 3 attempts to use Qubes OS have ended (1) All my VMs were either cloned a dozen times or destroyed. (2) I reinstalled Qubes OS from scratch and restricted myself to only disposable VM running only firefox. Then all of a sudden everything sporadically had its ability to access the internet stopped. A restart fixed this, but I concluded the safest thing to do was reinstall. (3) All ability for any VM to access the internet stopped. In fact it never started. I could not reach the internet while connected to the Wi-Fi. When I tried to restart sys-net VM my screen filled with a notification saying something like, āQubes Update unable to stop, errorā (or something along those paraphrased lines). I tried to reinstall this (4)th time just to see if it would connect to the internet and during installing I found 4 backup partitions inside the dom0, inside the lvm, on advanced partitioning present from the installation from the last install that I never created. I found that because the automatic partitioning āconfiguration failedā after I clicked āDoneā. Advanced partitioning failed as well. I had to install to a external USB SSD. Now shortly after bootup and login, the screen goes wacky then exits to the tty terminal from which i cannot escape except to restart. I noticed in an dot error log in the home directory had an entry with something interacting with ssh secure keyring along with a bunch of dbus errors and something like āgptā.xwindow.c āatom xā errors too. I do not know if that is relevant. And all files and folders in /var/log/⦠were completely empty, even though the files and folders were created by something, it was all barren.
Iāve switched to Qubes OS recently because no matter how hard I tried, my Windows (10 and 11) (and Linux [Ubuntu and Debian] and my Galaxy Z Fold3 5G [Android 13]) installations always get filled with logs of logins with elevated privileges, and processes and services (and daemons) with malicious code and control over my computerās and smartphoneās. The input and output kept getting overrun with oodles of scripts, programs, and virtual devices.
What am I overlooking? Could my Intel ME be compromised? I canāt reinstall again as my two ssds and usb ssd are somehow unable to be formatted by the installer usb and that is the only bootable usb I have. I am posting this via my smart phone.
I am running an Alienware Laptop M17, could there be a remote access subsystem placed by dell? Iāve seen dell environments, accessable from the boot menu, come with a full network stack. Could the SCSI subsystem be compromised and allowing remote connection? Could it be an āevil twinā wireless AP that can somehow connect to subsystem or some pre-enabled Qubes OS remote connection protocol such as ssh or qrpcexec (or whatever it is called). BTW that poses an unnecissary and extreme security risk. Qubes native dom0 remote connection implementation? What a perfect tool to easily and completely take over hard and fast, with little effort. It comes standard on every current release even though Iām sure less than 1% of any user would ever use? Why?? Canāt there be a version of Qubes that does not come with such a powerful tool for hackers and useless to me? Why isnāt Yubikey an option during installation and would it even protect Qubes from any and all possible remote connection attempts? How would I find and secure any possible subsystems and not allow any connection that isnāt solely me requesting https requests to websites? The firewall should have a https, dnssec originating from known authoratative DNS servers connections only feature preconfigured because the firewall seems to be useless to me unless I am missing something obvious.
Thank you for your time and I look foward to your insightful replies.