We’d rather like to see that anyways 😜.

Maybe I’m already running in XWayland somehow?

That’s definitely possible. Within Firefox, what does about:support reveal on this matter?

FWIW, I just noticed this thread

Unfortunately, I don’t own any device with Nvidia. Hence, I don’t think I’ll be able to help out. However, wayblue’s maintainers are pretty active. Therefore, consider opening an issue on its GitHub page and perhaps they’ll be able to help out.

I apologize for not being of much help here. Wish ya good luck, though!

Happy cake day btw!

Glad to be of help!

And thank you for reporting back!

Enjoy 😊!

It has been my pleasure!

It used to be called Sericea. However, the obscure names started to become very unwieldy. Therefore, they chose to preserve the naming for earlier established and recognized names (i.e. Silverblue and Kinoite) while Sericea became Sway Atomic instead.

It’s found here. It’s called sericea-nvidia. For this image, please refer to the installation guide found here if you’re interested.

Consider reporting back on how it goes 😉.

Ideally I would use an existing atomic distro with both Sway and Nvidia drivers

Consider taking a look at uBlue’s base image with Sway and built-in Nvidia drivers or wayblue’s image with Sway and built-in Nvidia drivers.

Thank you for sharing! If you remember, could you share your findings?

Hehe. I agree that the community on Lemmy gives off more mature vibes. I suppose one should at least credit them for being idealistic enough to be on Lemmy rather than Reddit.

Thank you for spreading the positivity 😄!

What would you need for convincing?

Probably explains why sudo dnf update/upgrade wasn’t quite doing what I expected in my Bazzite install.

Exactly.

Force of habit since I’ve used Fedora and Debian based systems in the past.

Understandable.

I’ve found it fine after an adaption phase

Though credit where credit is due. At this point, so well-beyond the adaption phase, I simply don’t see myself use anything else. This is my home. Though I have to admit my serious interest in QubesOS (and the upcoming Spectrum OS).

Hard agree on knowing the nuances being problematic, clarity and accessible education is sorely missing, certainly the steepest part of the learning curve.

Agree. I’m at least thankful that it’s a lot better than it used to be. Like two years ago, when as a total noob to Linux, I decided to cold turkey quit Windows and installed Fedora Silverblue on my machine. Well…, those first two weeks were pretty traumatic 😂. And, back then, there was not a lot out there. Luckily, I found this article that helped me to grasp the basics. And it has been smooth sailing ever since.

I just run ‘distrobox upgrade -all’ in my Daily.service

That’s pretty cool (and straightforward). Why didn’t I think of that 😂? But yeah, quadlets FTW.

Ehh I prefer system-wide installation.

Fair.

I think it’s a habit from times when installing an Android app with root (so the OS treats it as a system app) increased its performance.

Interesting. Didn’t know this was a thing.

I’m a big fan of Fedora Atomic. However, even I have to admit that knowing how to install packages through dnf is simply more convenient than knowing and understanding the nuances between rpm-ostree, Toolbx/Distrobox and flatpak. And I haven’t even delved into ujust and brew that are found on uBlue images.

Furthermore, even if we would limit ourselves with what Fedora Atomic prescribes, we see the following inconveniences:

• rpm-ostree ; I know --apply-live exists and I know systemctl soft-reboot exists. But still, if you have to resort to rpm-ostree, then both the speed of update/installation as well as the need to reboot (or live on the edge with --apply-live) are inconvenient compared to dnf.
• flatpak ; It’s inconvenient that I have to alias the installed package if I prefer sane naming conventions when accessing it through the terminal. Furthermore, stuff like the NativeMessaging portal not being available yet for sandboxed browsers and how that prevents any local password manager to interact with them (without hacking your way through; which, once again, is an inconvenience) is inconvenient.
• Toolbx/Distrobox ; the fact that you’d have to setup quadlets (or simply rely on uBlue images to do it for you) to keep them up to date, up and running is an inconvenience. The fact that distrobox-export has to be resorted to for accessing these directly from your ‘App Drawer’ is an inconvenience.

The fact that there’s no centralized place for upgrading all of the above (unless you rely on an uBlue image) is an inconvenience.

I could go on and on, but these should satisfy in revealing some of the more obnoxious inconveniences.

Thanks for pointing that out!

Bazzite also includes an entry in their documentation in which they explain how theming on Bazzite works exactly.

FWIW, by creating your own images (through BlueBuild or tooling offered by uBlue) you could bake themes directly into those folders.

However, I totally understand why you’d not feel compelled to do as such 😅. Especially if your current distro/system works splendidly.

Sometimes, placing it to ~/.local/share/themes works as well*.

Fair.

Btw, was I correct on the following?

I assume this is based on an experience with Kinoite? Am I right?

Thank you for the answer and for your time! I wish you a nice day!