I wondered this same thing and investigated installing Hyprland on Bazzite but didn't really find anything. I suspect you'd layer the installation into the os with rpm-ostree, but I didn't end up trying it.
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Yes you just layer all the packages. With an additional WM it is not a huge deal. But when doing entire GNOME on Kinoite that will make updates incredibly slow.
So using blue-build would be recommended here.
Can I run KDE and Gnome on bazzite?
Both GNOME and KDE Plasma are supported on Bazzite.
How can I install and manage multiple images?
Multiple images can only coexist as follows:
- Dual-boot
- Rebase to second image -> pin second image with
sudo ostree admin pin <insert digit>
-> rebase back to original image. From now on, you can access this second image from GRUB. It's recommended to designate a different user to the second image; and only access it through that. While what has been just described technically works, and you could even keep the second image up to date with a super cumbersome upgrade path, managing a system like this is not supported and could lead to unforeseen circumstances. Though, it is valid to pin your original image -> test another image through rebasing (and a new designated user) -> rollback to original image. Pinning the original image is not necessary, but I like to play safe. Note thatrpm-ostree reset
might be needed sometimes for rebasing.
Now I suspect that perhaps the game freeze wouldn’t happen with Gnome either. So I want to have both on bazzite, but can’t figure it out.
So, IIUC, you're just interested to know if this problem persists on GNOME or not. So, consider the following:
- Pin your current deployment with
sudo ostree admin pin 0
. - Create a new user, but don't use it yet.
- Rebase to Bazzite's GNOME image.
- Reboot
- Enter through the new user (or create a new one).
- Test out whatever you want.
- Rollback through
rpm-ostree rollback
- Reboot
- Continue using your original user.
Thank you for the detailed answer!
Based on all the answers I've recieved, I see that's it's probably best that I leave the DE alone. At the end of the day, I just need to make sure that I have the correct dependencies for the app in question. Installing the entirety of Gnome was really just my lazy fix idea.
You should be able to layer the xdg-desktop-portal-gnome
package, which will also pull any dependencies.
To answer your general question though, yes I believe you can easily install at least minimal versions of each DE with little impact to rpm-ostree performance. They don't need to be separate images, though that's possible too by rebasing and pinning. I would just layer the necessary packages to load a GNOME environment (start with rpm-ostree install gnome-shell
). This way everything stays up to date with the active image. For example, I'm running GDM under Kinoite simply because I was having unresolvable issues with SDDM and LightDM.
Pinning separate images would require you to rebase with each image update and then unpin/pin the old/new images...too much work.
Thanks! This sounds like the best way to do things.
I really appreciate the help. I'm going to spend some time learning about this, and your suggestion is where I'll start.
I'm not sure about the bazzite part, but running both kde and gnome is not typically recommended. Kde changes a bunch of theming and miscellaneous settings whenever you launch it, and gnome doesn't change them back automatically. If you only care about running one game rather than daily driving gnome you should be fine though
Thanks! I'm taking the advice of some other commenters about adding what I need without installing Gnome, which at the end of the day works apparently cause more problems that it solved.
I am running Bazzite and Stellaris. I have no issues with stability or opening the game. Have you checked your hardware fundamentals and done things like disable steam overlay?
Update: I turned off steam overlay, and set the in-game video setting from borderless full screen to just full screen, and that did it!
So much frustration, and such an easy fix. Ugh. But at least it's working now. Thanks again.
Thanks for the update! Glad to hear it's fixed; also thank you (on behalf of the community) for sharing the fix. If I may, I think this would be a classic example of the XY problem. Anyhow, wish ya a great day!
I haven't seen any hardware issues, but perhaps I'm just ignorant. I'm pretty busy with work and family generally, so I seldom dig into troubleshooting recently. I'm not even sure I'd know how to start with hardware diagnostics on an atomic distro (but that should be easy enough to find in the documentation).
I'll try turning off steam overlay, thanks for the tip!
Hahaha yes this is totally possible but not what you need.
Just do rpm-ostree search portal
and install the gnome portal on the KDE base.
Thanks! Just what I needed. The idea to install an entire DE was my lazy fix idea, but now I'm learning more about how atomic distros work, and finally using the terminal in bazzite! It is such a convenient distro, but it also felt wierd to never open the terminal.
Not much info on how to achieve it, but some info why it might be bad can be found on the ublue discourse site. (Search for KDE gnome) Basically it seems to mess up configs to have both DEs installed or rebasing from one to the other.
I've been curious about this myself.