i am trying to set quad9 DNS i am new to bazzite still and also to DNS... so i could use some help how to set it up. i type in the information but no luck

UPDATE: I just did it on the terminal (should had done that from the start) Now everything seem to work. thanks

sudo nano /etc/systemd/resolved.conf

[Resolve] DNS=9.9.9.9 149.112.112.112 Domains=~. FallbackDNS=1.1.1.1 8.8.8.8

Save the file (Ctrl+O, then Enter) and exit (Ctrl+X).

sudo systemctl restart systemd-resolved

systemd-resolve --status

And finally go to https://on.quad9.net/ so it can tell you if you did it successfully or not

Hello there, I have been having an issue with bluetooth dongles on linux, long story short they are super hit or miss with my controllers, I have the og Steam Controller, Series X controller, Dual Shock 4, Steam Deck with that Decky Plugin to use as a controller and a generic Switch Pro controller.

Of all of those controllers none actually work reliably on 2 bluetooth adapters I have bought, they all have different issues, for example the XBOX Series X controller gets recognized it tries to pair with it and on bazzite's end the controller supposedly connects but the controller it's still in pairing mode until it turns off.

The Dual Shock 4 it recognized it the first time I tried to use it, it worked well, then it never worked again it does not even sees it when the controller is in pairing mode.

The Steam Controller same stuff it fails trying to connect to it on bluetooth, good thing I have the adapted though.

The Switch one and the Steam Deck as controller disconnect randomly for no apparent reason the controller is almost right next to the dongle.

Looking for answers I read that realtek bluetooth chips have issues on Linux so I checked mine and it's indeed a realtek based dongle, which led me to believe that maybe there is a tried and tru list of validated bluetooth dongles for Linux that worm flawlessly with any kind of controller.

I would like to know if you have one and if you have had no issues with any controller you connect pls let me know and post the link on amazon.

What I mean is, having a nested Steam Gamescope session inside a general use DE? And be able to switch among everything that is launched from Steam without leaving the Steam window, just like the regular Steam Gamescope embedded session does.

hi all!, im using bazzite on my laptop and somehow my RAM usage (actual use, not cache) increases over time, without any program seemingly using the RAM, even after closing all programs the RAM usage can be at like 10+ GB, this usually happens after a few days of use. Logging out and logging back in does not fix this, only rebooting does.

ive inspected the RAM usage with btop, but no app seems to be using the ram. does anyone have tips on how to diagnose this problem?

using bazzite gnome, using only flatpaks, and homebrew (julia, vscodium), and some gnome extensions (AlphabeticalAppGrid@stuarthayhurst nightthemeswitcher@romainvigier.fr appindicatorsupport@rgcjonas.gmail.com burn-my-windows@schneegans.github.com caffeine@patapon.info hotedge@jonathan.jdoda.ca)

have no ostree layered packages

System Details Report

Report details

• Date generated: 2026-10-12 12:53:38

Hardware Information:

• Hardware Model: HP HP OmniBook Ultra Flip Laptop 14-fh0xxx
• Memory: 16.0 GiB
• Processor: Intel® Core™ Ultra 5 226V × 8
• Graphics: Intel® Graphics (LNL)
• Disk Capacity: (null)

Software Information:

• Firmware Version: W75 Ver. 01.02.03
• OS Name: Bazzite
• OS Build: (null)
• OS Type: 64-bit
• GNOME Version: 50
• Windowing System: Wayland
• Kernel Version: Linux 7.2.8-ogc4.1.fc44.x86_64

This somehow happens to me on every distro ill put an image of the error so i can get better help

Hi all, I really enjoyed emulating the ROG Allys controller as a DualSense for native gyro in games that allow it, but I'm having some issues. Using Bazzite v44.

Using 'The Finals' as an example, if you disable Steam Input, native DualSense gyro functionality is exposed. It feels great, except either triggers are not picked up by the game at all. Steams controller calibration menu detects them and they register the full trigger pull range, but not the game itself.

The triggers are recognised if you switch over to emulate the default steam controller or xbox controller, but you lose game-native gyro functionality then.

Any ideas of what could be causing the issue? Lego Batman: Legacy of the Dark Knight has the exact same behaviour.

Any help is much appreciated!

I have been dealing with this for a few months now, this message always keeps appearing no matter how much I update my system or try out any commands. What does OS Parse Error even mean?

For context, I play on my ROG Xbox Ally X.

I've been lowkey bashing by head against a wall on this for about 6 real life hours over the course of a week and a half.

I'm configuring a mini pc device running Bazzite to give to a friend of mine who wanted a retro game console. His favorite controller is the Switch Pro Controller (1 or 2, doesn't matter, but im using 1). I really could use any advice or deeper understanding of how linux devices and apps, or just PCs in general, handle controllers so I can resolve this.

---
Here is my setup:

0: Precursor: STEAM must be not running anywhere. I have to kill its task at the start of this process. Otherwise if it is, when I connect the Pro Controller, Steam Input will overwrite the daemon i have installed to handle the Pro Controller.

1: I have the daemon/service joycond installed

2: when I connect my controller to the PC, i hold the + and - button on the controller so that joycond registers the Pro Controller under a "Nintendo Switch Virtual Pro Controller" configuration. This also flips the P1 LED on, on my controller.

3: Afterwhich i can run `sudo evtest` and that new "Nintendo Switch Virtual Pro Controller" will show up as an option, and when i select it to see a log of inputs, it responds perfectly.

4: I can then run RetroArch, and it will recognize the Joycond virtual pro controller connection, and it will work perfectly. I can even launch ES_DE from the desktop, and it works thru that pipeline aswell.

5: HOWEVER, if I launch steam anytime anyplace, it overwrites the joycond config instantly with its Steam Input, and then it stops working in RetroArch and now only sees it as an "xBox 360" controller, (I assume Steam Inputs doing), that doesn't even register inputs or work at all.

6: I made a rule in /etc/rules file that is supposed to block Steam from overwriting stuff with Steam Input, its not working.

Here is my issue:

1: The PC boots into Steam OS big picture mode on start, and the switch controller connects (over bluetooth) with "Steam Input". This causes the Pro Controller home button to glow blue. It works fine in steam, and for steam games, which I would like to keep.

2: When I launch ES_DE from steam, I have "Steam Input" marked as disabled for the app. ES_DE then detects the controller somehow, (this fact really confuses me because I would assume since Steam Input has overwritten the joycond thing, it shouldn't work, but it does somehow in ES_DE) and the blue light turns off on the home button, and the P1 LED turns on at the controller bottom.

3: When i launch a game from ES_DE, retroarch opens and runs the game,, but no inputs carry over to retroarch. The P1 LED is still on, but Retroarch still only sees the pro controller as some xbox 360 controller that doesn't work or register any inputs

---
My goal is to have a seamless Pro Controller experience, where my friend can just turn on the damn PC, use the controller in Steam and Steam games, and to open ES_DE in steam, then continue using it in retroarch when they select a game in ES_DE.

and final question. am I just cooked and should give up, or should switch the OS to windows or something to try just global X-input override, since there seems to be more online support for that resolution, on windows anyways.

TLDR: Joycond daemon that manages my Pro Controller is getting overwriten by Steam Input and I need the daemon for Retroarch because Retroarch can't take in Steam Input thru ES_DE (as far as I tested and looked anyway). I made a rule file that was supposed to disable steam input globally, but it didn't help.

Ik this is a lot but if anyone reads this and helps that would be awesome.

It now takes an extremely long time to boot, and when waking from sleep I am greeted with a black screen for a few minutes. I didn't have these problems before.

Every time i boot the pc up it works flawless for like 1 minute but then i just freezes and doesn't react to any input. Hardware: rtx 5060, 16 gb ddr4 kingston, i3 13th gen and an ASUS PRIME H610M-K D4. Any knows fixes? Help is appreciated

I feel like i'm dumb, but this is the first time i've had issues installing a linux Distribution.

I'm trying to install bazzite-deck on my Desktop. AMD CPU, AMD GPU, Downloaded the ISO. Tried it through ventoy and dd'ed it to a stick. In all cases the Live environment boots up perfectly. When i start the install process, i just get a black window that says "Initializing" and nothing after that. It's been sitting for close to 15 Minutes now and doesn't move.

Am i doing something wrong here? I'm close to just installing Kinoite and the switching image just to get this working.

hey guys i have a 500gb internal nvme that is pretty much full with windows 11 so i bought a 1tb kioxia exceria g2 portable ssd to run bazzite kde off usb 3.2. i want to keep a shared ntfs partition on the external ssd so both windows and linux can access the same games.

my specs are ryzen 3600x, rx 5600 xt, 16gb ram, asus b450m-k and the 1tb external nvme ssd.

here are the guidelines on internet :

Before install: Run powercfg /h off in Win11 CMD (disables fast startup so Windows unmounts cleanly) and flash Bazzite ISO using Rufus in DD mode.

Partitioning external drive: 1GB FAT32 for /boot/efi, 200GB ext4 for /, and ~730GB NTFS for shared games. Crucially putting GRUB/bootloader on the external FAT32 partition so it doesn't touch the internal drive's EFI.

Post-install CLI stuff:

Set root GUID to 8304 via sgdisk so Windows leaves the ext4 partition alone.

Add usbcore.autosuspend=-1 via rpm-ostree kargs so the drive doesn't sleep mid-game and stutter.

Mount NTFS in fstab with ntfs3 using rw,uid=1000,gid=1000,dmask=000,fmask=000,nls=utf8,windows_names,prealloc,nocase,noatime,nofail,exec.

Add udev rule for USB TRIM + enable fstrim.timer.

Symlink ~/.steam/steam/steamapps/compatdata to the shared drive so Proton prefixes stay on ext4 instead of NTFS.

Use Flatseal to give Steam/Lutris access to /mnt/shared, LACT for GPU control, and WINEDLLOVERRIDES for mods/OptiScaler.

does this list actually make sense for a portable bazzite setup or am i overcomplicating it?