Ta good way to test is if a nvidia user chooses the breeze theme instead of the default which is vapor
Tvapor shouldn't change that much to be causing this though?
TIt's funny, back about 12 years ago, they were the best experience because their drivers worked well on X11 and the others just kinda sucked.
Tyeah they were like the only ones who had proper driver support on linux lol
Tbut now that the other vendors have open source drivers, its the total opposite experience
TAnyone had issues with sleep recently? I’m running Bazzite-Polaris with the older Gamescope version, and immediately after entering sleep my fans will ramp up and the PC wakes again. There’s a good chance it’s a hardware problem on my end, i figured I’d ask first though.
QI have a slightly more philosophical question, since everything I've tried so far has mostly just worked. How are people managing machine configs long term, especially across updates? I've been using NixOS on my home lab servers for a while, and now every time I manually edit something on my new Bazzite gaming machine, a little part of my soul dies. It's only been a week and I already feel like I couldn't get back to the exact same state again if I reinstalled.
Achezmoi work pretty good for me, also usually update unless major wont break config right?
QI'm still using home-manager and nix to manage my personal home environment, but I meant system level things. Everything from hostname, to sshd and tailscale configs, automounts for my NAS shares, etc. All those little things you slowly build up over time. With NixOS, all that's described in a (set of) config file(s) that's built into a system, and the only way to "apply" it is to build a new generation and switch to it, so you inherently have a full description of what changes exist from the system defaults.
Afor that you can create your own custom image i think?
Ayou can just base it off bazzite and add things you need like package, configs, service, and such
QWould that be something that can sit atop the standard Bazzite
just update or whatever, or would you need to rebuild your image every time you wanted the latest Bazzite updates?
Kif you fork you need to pull our changes
Kif you make an image FROM then every time it builds (shcheduled in github) your changes are applied on top of our latest
KBazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
QHrm. That's not quite the sort of workflow I was envisioning, but it might work. I'd have to use standard shell scripting or some other similar tool in the context of the Containerfile to put the various changes in place. I suppose what I was looking for was a ublue/bazzite sort of equivalent to Arch's aconfmgr.
Aif you dont like using containerfile directly you can use bluebuild and have your config almost declaratively
QOh, it wasn't really a problem with containerfiles. It's just the suggestion solves the problem at a different level than I had originally thought about approaching it. I was thinking of a tool that I would run on top of an existing Bazzite build to ensure that the things I wanted configured. A bazzite-aware Ansible role or as I mentioned, aconfmgr for ublue-based distros, or similar. I hadn't thought of making the image itself custom.
Acustom image in atomic/immutable distro are kinda equivalent to aconfmgr i think? because the normal distro way and atomic distro way are kinda different
Amostly because not even sudo can write to some directory
QYeah. That's why I asked the initial question. It's different from the other sorts of systems I've administered in the past, so it feels like a lot of my normal tools for solving the problem aren't appropriate.
Aalthough maybe it is possible to have something like that if you dont need to touch stuff like /usr
Gis anyone else not able to get to the desktop on bazzite KDE?
QThus far it's not been anything like that. Mostly things in etc; configuration of already installed services like sshd and tailscale, adding and enabling systemd units for things like automounts, etc.
MWas using it for Jellyfin earlier everything worked for me as normal
GI'm thinking of just reinstalling but I can't get to the KDE desktop
Aim using bazzite kde rn, nothing weird for my system
Gyeah not entirely sure what's going on here
_Hey there, not sure if this is the appropriate place to ask but I was messing with GPU settings, applied them, and got a black screen. No big deal, rebooted, still black screened. Did some reading and saw people suggest ctrl+alt+f2. That worked for me to get my display back. Problem now is that it does this each time the PC reboots. Was hoping someone here had some insight as to what I could do to fix it. Relatively new to Linux
KNvidia?
_AMD
TGetting this as well
CAre you on newest update?
TYep fresh install as well
CI kept checking after each update and one of them fixed it and i haven't updated it since
TMight switch stable to beta
Cshould prob pin this update
COh also I am in Steam Beta for the Steam Families
TAh that’s prob it I’ll give it ago now
CAlso curious if decky loader has an update, i miss the plugins
TAh I’ve heard somewhere that you could install preview decky builds that work with steam beta
CI have it, just googled and realized need to switch to steam stable to switch to decky prerelease and then swtich to steam beta
TOr yeah do it within decky haha
TYep that sorted the issue
CAnybody else getting a black screen when they login after boot with multiple monitors attached? Login screen shows just fine but after logging in I get a completely black screen until I manually disconnect one of my monitors. Plasmashell shows a segfault issue in the crash log.
SGood evening guys, So I've run into a weird issue when importing my steam libraries, etc.
Basically I have three drives, My 240 gig sata ssd for bazzite. A 2tb nvme for windows 11, and a 5tb external hard drive for media and larger games. The latter two are ntfs while the sata ssd is butterfs. I did read the documentation and I understand that importing ntfs game libraries is a bad idea bc incompatibility but maybe this is a good example of why specifically?
For some reason my copy of Proton 9.0 installed on my external hard disk and it's stuck asking for it to be updated. When I try that, It mentions that there is a disk write error and that proton is using zero bytes in the game folder. I also can't uninstall it or move it elsewhere?
I've also tried switching proton versions in the steam compatibility settings menu with no dice since it's still relying on the 9.0 version to some extent.
Basically I have three drives, My 240 gig sata ssd for bazzite. A 2tb nvme for windows 11, and a 5tb external hard drive for media and larger games. The latter two are ntfs while the sata ssd is butterfs. I did read the documentation and I understand that importing ntfs game libraries is a bad idea bc incompatibility but maybe this is a good example of why specifically?
For some reason my copy of Proton 9.0 installed on my external hard disk and it's stuck asking for it to be updated. When I try that, It mentions that there is a disk write error and that proton is using zero bytes in the game folder. I also can't uninstall it or move it elsewhere?
I've also tried switching proton versions in the steam compatibility settings menu with no dice since it's still relying on the 9.0 version to some extent.
KCheck if its mounted read only, sometimes Linux mounts Windows drives read only
Wiirc proton tries to mount folders like z:/ and c:/ when it's starting up the game, when you using ntfs, the colon character is an illegal character in ntfs, so you have to do a bunch of hacks to get proton to work correctly with ntfs. Just in general Ntfs and Linux don't worked that well together. So while it's definately possible to use ntfs for your games it's more of a hassle than what it's worth imo.
CSteam Beta broke Protontricks
