TheGodfather Years and years ago, I tried Ubuntu. Didn't like it and went back to Windows. Then I tried Mint (Cinnamon) for a while. That was OK, but, again, I went back to Windows. Then Fedora (almost a year, I think, before going back to Windows). A few small attempt in there as well. This time around, I thought an Atomic version would be interesting. Plus, Bazzite being already set up for gaming might make it doable for the wife if I could get it to work. My first attempt with that (during the forced migration from Windows 10 to 11) failed with issues getting Yubico Authenticator and multiple Brave profiles loaded. With Microsoft moving to an "agentic" model in Windows, I decided to try Bazzite again (this time very slowly, so I wouldn't get burned out). But, without being able to get Auto-Type working in my local password manager, it's just a flatout no-go.
I can't find when it happened, but it looks like they removed Xwayland support in Bazzite. From what I can gather (but, remember, I'm basing this on bits and pieces that pop up in internet searches -- I can't find official statements), it was removed in either Fedora 40 or 41 and Bazzite is based on Fedora. Also, it also looks like KDE separated X11 and Wayland in Plasma and Bazzite (recently?) chose to use only the Wayland side of it. All the various ways I could find on getting X11 stuff to work in Bazzite were either no longer there or didn't work.
avaluedcustomer I'd seen that plugin. But, as you mentioned, it doesn't help with desktop applications. Which knocked it out of the running for me.
Supposedly, there's also setting an environment variable (QT_QPA_PLATFORM=xcb) or starting KeePassXC with the platform xcb command-line flag. I tried the environment variable route and, following a reboot, it basically cleared my desktop of all controls. I pulled the line back out of my .bashrc file and everything came back.
Anyway, that's all specific to my travails. The real issue is that X11 is dead and Wayland will soon be the only thing supported. And, Wayland is specifically designed to prevent things like Auto-Type. And, currently (without something like a Password Manager API or some better way to do it), that makes local password managers unusable. What I don't understand is that there's almost no discussion of this. Surely, Linux users don't use a limited set of remembered passwords instead of password managers. Surely, they don't all trust their passwords to cloud-based password managers instead of running them locally. It's not even possible to move away from password managers to things like hardware keys or passkeys (not everything supports them and passkeys seem to be on a vendor lock-in route).
I've seen a comment or two about developing an API for password managers to use to securely communicate to applications. But, even if that happened, it would be years in the making. But, without it.... Well, it doesn't bode well.