Thank you for the warm welcome!
This is the first thing I thought when I saw the message, but I wasn’t sure how that command is supposed to have an effect, because that message is shown before the disk is unlocked, and AFAIK systemctl daemon-reload is meant to make running systemd aware of updated service files. But I haven’t seen the message in a while and it’s not that important anyways.
Most likely, yeah.
Now this is something I hadn’t thought about, but it makes sense.
That’s exactly the kind of thinking that kept me sane all this time: that whatever it is, Qubes OS’ isolation will (probably) keep everything safe.
This was an interesting read. Makes me wonder, whether something like this has been documented as being used by an adversary to recover data.
Thanks to everyone who replied~ Now that I know who the main culprit might be, I might give the good old integrated graphics of my CPU a try with Qubes OS, and see if that fixes these issues. I don’t think it’ll be a “downgrade”, since the GPU isn’t being utilised by appVMs directly anyways.