Every once in a while a security researcher will highlight a new method for obtaining the key from the TPM, usually by tapping into the I2C comms between it and the CPU. They'll say it's 'trvial' and can be done 'in seconds', but that's only after a lot of work figuring out that particular motherboard.
A few months ago there was yellowkey that just needed a special file on a USB drive to bypass bitlocker, making it so easy that it was arguably a backdoor.
Depending on how the cables have been put in, it can be fairly easy to replace an existing run by tying the new cable to the old one and pulling it through.
I'd be worried about lateral movement. Something like a XSS in jellyfin that gets them to my browser on my main computer, or otherwise leveraging the network proximity in anyway to spread to other machines with stuff I care about.
OMG is that Horridus, the most complete Triceratops fossil known?
Even worse, the card's model is '7G106', 7G100 is the series, like saying NVIDIA RTX 5000 series of cards.
Very evocative of the 2010 Motorola Flipout I still have in a drawer. Looks very fun.
Gotta preach for the cult of ZFS. It's check summing, copy on write, and zraid features are all exactly what you want for data resilience. Plus you get transparent compression, and snapshots that can provide a bit of a stop-gap for your lack of backups.
It will normally soak up any and all memory for buffers and caches, but is meant to quickly free up when it's needed by an app. Linux already does this on any filesystem with its page cache.
Oh and mounting a ZFS dataset on a new machine is super quick and easy, it stores it's config on the drives themselves, so you can plug them into a new box and zpool import -af and boom it's mounted and ready to go.
Didn't know Doc Martins did Chelsea style boots, that's sick!
I keep buying and wearing out various no-name cheap boots. One day I'll get a pair of RM Williams or even Crockett & Jones...
I remember when I was a kid messing with Windows 95/98, I had this intuitive feeling of what was happening under the hood. Just like how you describe your theory. Honestly you're probably on the right track. In theory on linux you can actually dive into the source code and try to figure out what's actually happening, but that's intimidating AF. Hard to say if the problem is between wine and the Direct Rendering Manager (DRM), X11, Wayland, KDE, or the GPU driver...
I had a kind of similar problem with my display not outputting when it was connected. I had to use a DRM file in /sys and udev script to fix it, wrote a blog about it. If your monitors are still messed up after a reboot, it sounds like this won't help you though.
Also you made me lol to "wine strikes me more as an emulator". It totes is. The "Wine Is Not an Emulator" name is a joke, the original name was "WINdows Emulator", which they changed to avoid Microsoft's lawyers.
That is simultaneously ridiculous and amazing. Blindly clicking the buttons to enable the screen definitely proves you're getting familiar with the OS.
Why do you think wine/Bricklink messed it up in the first place?