That's the nice thing about this Verge mention, the more attention we get, the more people like us will show up, which means we can fix more stuff. The virtuous circle.
On mine I have to attempt opening the app twice. So: Boot > explorer > wait a bit > explorer again. Do let me know what you can and can't fix I'll update the guide
@dannymate Ok for some reason I don't think it ever "makes" the container? Because if I then try to use "start" it just says no winapps container exists
yep, i get that it's mostly outside of your control. and thankfully rpm-ostree makes it trivially easy to rollback i'm just not as gung-ho about updating as I was before
I think what you might be seeing is the difference between GPU power and total board power. The 140w rating from the spec sheet may be the total power draw of the card including memory, fans, and everything else. 115w may just the gpu die by itself.
I appreciate the response. It’s 115W base TDP with a 25W boost, in windows the GPU draws 140 no problem. It’s a Linux thing I gotta figure out. I’ve read before that TDP boosts can be weird in Linux
Messed around yesterday and managed to install and get Niri working via layering, had to install xwayland-satellite for steam to work and there was some funky stuff which I believe is due to the general Nvidia driver wayland support. Had some issues with plasmashell loading alongside niri when selecting it in SDDM, and then had to recreate my user because it completely borked logging into the plasma session, but it was a fun couple hours of fiddling. May try my hand at making a Niri fork if I can manage to wrap my head around all of the cosign and build process stuff