Oh sorry I misread, so it always opened internally regardless of that setting? That could be worth a bug report on their repo if you have the time (and can reliably reproduce the behaviour). Could be a quirk with Firefox for Android as well, though.
Huh, that sounds nasty. Does the flickering stuff happen with specific games or just any game you play? If you haven't switched back to windows already, do you think you could capture a small clip of this happening with an external device?
I have similar hardware to you. I haven't seen anything like this with gnome + Wayland but I can try groupinstall KDE on fedora to see if I can hit this too.
Do you have the app internal browser (custom tabs) enabled? Open link shows it in the app browser, open link external pops it open in firefox.
I suppose we could make a request to hide the 'open link' option from the list if the custom tabs feature is disabled? Perhaps we could also include a tooltip for the custom tabs feature to convey that is works as the in-app browser.
Similar if not practically identical chassis to my T14 Gen2a. My one is Cezanne based and the experience with fedora/wayland/gnome has been perfectly smooth. Did you spot any logs relating to those issues?
Can't say I've experienced any such issues on recent AMD UMA or dGPU systems; power management is pretty well documented and generally reliable without any need for user intervention. Curious as to which platforms were problematic in your experience for my own learning; it's likely that anything pre-polaris was kind of wonky
I've also not had any issues with Intel integrated graphics on Linux, but ANV on Arc is a bit messy with translation layers like vkd3d right now. The gen12 (DG1, RKL and later) driver & technology stack appears to be quite different.
Primarily use AMD graphics. My key issue on linux is the GPU reset situation, which can make experiences like VFIO and LookingGlass less than optimal, though there seems to be some commitment from all IHVs to improve desktop expeirence under Linux.
AMD and Valve work fairly closely on such endeavours which is neat, though we also have nvidia getting their shit together for Wayland and now offering an open kernel module (even in lieu of open, first party UMDs, for which the NVK driver is well worth investigating).
The open kernel module and NVK driver are applicable to Turing (your current GPU) and newer. Check them out.
You don't owe it to anybody to align to a given vendor, just use what works best for you at a price point that doesn't suck. If there are any specific use cases you'd like to know about then I'm sure the people here would be happy to test and report back.
o shit I was expecting merch lol