I’ve been using Aurora which is an immutable distro based on Fedora. It’s from the same guys who do Bazzite. I use it on my work laptop with a discrete Nvidia card. I’ve had zero issues with the video driver. (I use Bazzite on two desktop and a laptop at home, all with Nvidia cards).

I really like these universal blue distro because on the odd occasion that I have an issue after an update, I can reboot into a pinned working version of the system. There are only a couple of CLI commands to learn to pin and unpin the different systems. All currently available systems appear on the grub menu. It’s kind of brilliant IMO.

Only downside is that installing RPM packages isn’t recommended, but I’ve found pretty much everything I need through flathub. I have one RPM package installed for VeraCrypt (no flatpak and it doesn’t work right in a container) but it hasn’t caused any issues for me.

Edit: I should say I can’t speak to the ongoing driver issues on the 50 series cards. The newest card I own is an RTX 3080 LHR 12 GB.

Forgot to include the boot/system volume. It’s a lovely time waster when you’re dealing with disk images that are hundreds of gigabytes in size that have to be copied over the network. 😆

I’ll add Disk2hvd screenshots when I get a sec.

Situation gets slightly more complicated if you had multiple drives in your system when you installed Windows, of course. Installer might put system volume on a different drive, so you’d have to image more than one drive to get a working system. Might get a little confusing as to which volumes should go in which image. There’s a tool called GWMI that might help with that since afaik the volume guids don’t show up in the Windows Disk Management snap-in.

Edit: The promised screenshot. In my case, I knew the volume labelled SYSTEM resided on the same disk as my C: drive. Probably don’t have to include the recovery partition, strictly speaking, but I did.

Well before today, I’d never heard of virtio-win, and I’d never used KVM/QEMU for virtualization on Linux, and despite an error on my part I had a running VM by close of business. Thanks for stopping by.

Oh wow! Thanks for this. I’m learning.

Oh huh. Is that a QEMU option? I’m new to all this.

Indeed I do.

FWIW I had the same issue under Fedora 40 Bazzite. For a bit I was having to shut down to avoid the problem you describe, and then they changed something else and I couldn’t even shut down cleanly from within the DE. Things have been sooo much better since the upgrade to 41.

I ran into this today using ssh-copy-id on a new Debian box. Seems like that tool is biased toward copying a second key instead of a first. Either that or they assume most users use one key pair everywhere (and thus only have one loaded in their agent). I use one key pair per user per box. Excessive? 🤔

I’ve slept since the last time I set up sshd on a new install. Do you need to be able to authenticate with a password when you ssh-copy-id on a user without a public key?

Edit: Silly me. Yes, password is required.

When I installed Bazzite on my Asus laptop I got an Armory Crate application. There seems to be something similar for MSI laptops called MControlCenter, but don’t know anything about it. Hope this gets you going in the right direction.