OneQuarterLife posted the following on Reddit:

We've switched to a fork of Waydroid that supports Nvidia GPUs. If you've already initialized Waydroid you'll need to reset it and initialize it again, but after doing so you can finally enjoy Android apps like AMD/Intel users have.

• Run ujust configure-waydroid in the terminal.
• Choose Reset Waydroid.
• Choose Initialize Waydroid.
• Finish the Waydroid configuration.
• Select your NVIDIA GPU in the GPU selection menu.
• Stop the Waydroid session: waydroid session stop
• Run the NVIDIA setup manually: sudo waydroid-nvidia-setup
• Enable and start the required services: sudo systemctl enable --now waydroid-container.service && systemctl --user enable --now wd-venus.service
• Start Waydroid.

Thanks to damin13 for the friendly instructions, we'll make this friendlier through ujust in the near future.

🔴 Tipp Betriebssystem für Gamer: Bazzite

Das Betriebssystem für die nächste Generation von Gamern
Bazzite macht Gaming und die alltägliche Nutzung auf Desktop-PCs, Handhelds, Tablets und Heimkino-PCs reibungsloser und einfacher.

➡️ Spiele deine Lieblingsspiele
Bazzite ist sowohl für Linux-Neulinge als auch für fortgeschrittene Nutzer konzipiert und bietet Steam vorinstalliert, HDR- und VRR-Unterstützung, verbesserte CPU-Scheduler für reaktionsschnelles Gameplay sowie zahlreiche von der Community entwickelte Tools und Optimierungen für ein noch besseres Gaming- und Streaming-Erlebnis.

https://bazzite.gg/

@bazzite.gg @bazzite

How do i trick battlefield 6 to run in bazzite? Dont tell me there is no way. I cant deal with this negative energy right now.

Hi pals! When writing this post out I realized the answer is probably "it's not ready yet" but hey, can't hurt to ask. Does anyone have any ideas on how to get KDE Plasma Big Screen on Bazzite? I'm not sure it's it's in usable shape but I would really like to try it. It's in weird territory - I saw reports it would be added natively to KDE Plasma 6.7 but I can't find it on my desktop running Fedora 44 w/ KDE Plasma 6.7.5.

Going through this page on the Bazzite docs:

1. It's not in the Bazzite Portal
2. Not in the Bazaar Store (I don't believe there is a flatpak version)
3. Homebrew doesn't seem to be applicable
4. Containers seem like they wouldn't be quite right since it'll have a lot of KDE dependencies.
5. I don't believe there's an AppImage of it.
6. rpm-ostree isn't recommended, last resort, etc.

It may just be too early for this but I figured I'd ask - don't be afraid to just say it's too much of an ask right now 😅

EDIT:

At least for the short term, rpm-ostree has worked! I ran the command:

rpm-ostree install plasma-bigscreen

The package took a few moments to install but so far it's working well - I was able to open KDE Plasma Bigscreen, open Emby, watch a video, and then exit Emby without having to use a mouse.

Whether or not I'll have issues updating things in the future, which is noted as a possible outcome of using rpm-ostree here, who knows!

Are you guys still getting this text-style JSON output when running ujust update?

Is it safe to rebase to steamdeck KDE image? Or do i have to reinstall the whole dang thing? It'll rustle my jimmies but i'll live.

Using bazzite 44 on steamdeck and i downloaded foot term from Bazaar and i wanted to use my own .ini file for it. but it doesnt seem to think that foot i s installed even while im using it. I created a file at ~/.config/foot/foot.ini and i ib looked at /etc/xdg/ there was no foot directory.

I use Bazzite in the living room, connected to the TV for gaming primarily.

KDE Connect still operates but can't be used for mouse (and possibly keyboard?) input any more. Something to do with the fedora base no longer supporting what it needs from what I've read

Is there an alternative? It was very very handy for the few occasions I need keyboard and mouse

#Alza, the largest online retail store in Czechia (often nicknamed the 'Czech Amazon'), has started selling gaming PCs with #Bazzite pre-installed. Congratulations to the @bazzite and @UniversalBlue communities - this is a big thing!

https://www.cnews.cz/clanky/cesky-steam-machine-je-tu-alza-zacina-prodavat-herni-sestavy-s-linuxem-ktery-je-skvelou-nahradou-za-windows/

#linux #gamingonlinux

We have a Bazzite box that different family members often use for streaming to their own laptops/computers from. It's cumbersome having to walk to the room it's in to wake it from sleep or log in their user into Steam on so that a Remote Play session can be started.

Created a little utility that runs a web service on the Bazzite box that can switch the logged in Steam user (guardrailed so that no switching can be done if someone is currently playing).

Additionally the binary (Windows, macOS and Linux) can run as a cli to do the switching, as well as sending a Wake-on-Lan packet and perform Steam Link connect PIN pairing.

Note: This is very early, only tested on our own system at the moment. It might also work on plain SteamOS with very little adaptions, that is completely untested though since I don't have such a machine.

Source repo for building (no ready binaries until I know it works for others too): https://git.sync.wtf/troed/bazinga

cross-posted from: https://literature.cafe/post/33779669

Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg

My prediction: bazzite may have more installs than Fedora KDE by the end of the year.

Important!! This is for Bazzite 43. I am working on Bazzite 44 but it will take some time. I mostly have it done, small bugs are being worked out. Bazzite 44 introduced some issue with this script, sorry!

This project started out of frustration, and quite frankly, there could have been a lot easier ways to go about it. But this is truly what I love about Linux, and it has always been the angle I come at it from: sideways, but practical.

For some background, I come from a time when community guides just like this one got me through some very tough times in Linux. Coming from highly obscure distributions like Yoper, building things for myself out of sheer necessity was a must. I hope someone finds this useful, and either builds off it or shares it with others who need it. If you are feeling friendly, please feel free to share this with the Reddit community. I no longer have an account there, but with all the fun little scripts popping up over there lately, I am sure some of you do. Ultimately, I just felt like the Lemmy Bazzite community needed some more content!

I am going to call it closed on my end because it is working just the way I need it to: you trigger the script, the lights turn off, and the system sleeps. Press the system power button, the system wakes, the OpenRGB profiles load automatically, and I am right back to gaming. Happy gaming, Bazzite dudes!

Yes me and my little ai buddy worked on this.

This guide provides a reliable solution for an issue in Bazzite where motherboard, RAM, and case RGB lights remain illuminated, flash, or cycle colors when the system enters sleep mode, and lighting profiles fail to revert back to your custom OpenRGB settings upon wake.

By implementing a user-space automation script, you eliminate the need to enable restrictive BIOS power-saving states (like ErP). This allows you to keep your USB ports powered overnight to charge controllers and peripherals while ensuring your room remains completely dark during system sleep.

Path Customization Note

Throughout this guide and within the script configuration variables, the directory path /home/gamer is used as the standard system baseline example. If your Bazzite configuration uses a different username, replace gamer with your actual system username across all directory paths, script entries, and terminal commands to ensure the automation executes correctly.

How It Works

When triggered from your Steam library, the script manages your system's transition into and out of sleep mode by handling hardware lighting configurations in an automated sequence:

• Before Sleep: It automatically darkens all hardware lighting components via OpenRGB.
• During Sleep: It safely initiates the operating system's suspend sequence while leaving USB power lines active for charging and peripheral wake signals.
• Upon Wake: It waits for the USB devices to stabilize, then automatically restores your default lighting profile in the background, ensuring the Steam Game Mode interface never experiences freezes or lag.

This script integrates into Steam Game Mode as a Non-Steam shortcut. It intercepts the sleep command to darken your hardware before allowing the system to suspend, preventing interface freezes and ensuring a clean foreground exit when the system wakes.

The Prerequisites

Before deploying either script version, your system must meet two initial setup requirements:

1. Install OpenRGB via Bazzite Portal

OpenRGB must be installed natively through the Bazzite Portal (or via the terminal command ujust install-openrgb).

Important: Do not install OpenRGB as a standard Flatpak from the Discover software center. Flatpaks are sandboxed and lack the low-level kernel hardware rules (udev) needed to communicate with your RGB controllers. The Bazzite Portal installation correctly configures these hardware permissions inside the operating system.

2. Configure Your Lighting Profiles

Open the OpenRGB application on your desktop and save two distinct profiles with these exact, case-sensitive names:

• off – A profile where all zones, devices, and components are set to black (turned off).
• on – Your standard, everyday operational gaming lighting profile.

The Core Concept: Why AppImage Extraction is More Reliable

If an AppImage is launched immediately before suspend, the interaction between FUSE mounting and the suspend process can occasionally prevent OpenRGB from starting cleanly. Extracting the AppImage avoids this dependency by executing the native AppRun binary directly.

To maximize execution reliability, both solutions utilize the AppImage extraction flag (--appimage-extract). Extracting the AppImage into a regular folder structure exposes the native executable named AppRun. The script launches this binary directly in user space, making suspend behavior significantly more reliable and ensuring a clean power transition.

Choose Your Strategy

Select the implementation path that best fits your system maintenance preferences.

Strategy 1: Manual Mode (No Auto Update)

• Who it is for: Users who prefer complete control over their filesystem and do not want automated scripts moving, changing, or interacting with application folders in the background.
• Maintenance Requirement: Whenever you update OpenRGB via the Bazzite Portal, you must manually open the terminal and re-run the extraction command to update your script's execution folder.

#!/bin/bash 

# --- Configuration Variables --- 
OPENRGB="/home/gamer/AppImages/OpenRGB-extracted/AppRun" 
CONFIG="/home/gamer/.config/OpenRGB" 
LOG_FILE="$HOME/openrgb-sleep.log" 

# 1. Log Rotation: Prevent the log file from growing infinitely 
if [ -f "$LOG_FILE" ] && [ "$(wc -l < "$LOG_FILE")" -gt 500 ]; then 
    # Keep only the last 200 lines of history 
    echo "$(tail -n 200 "$LOG_FILE")" > "$LOG_FILE" 
    echo "$(date '+%Y-%m-%d %H:%M:%S'): Log rotated to prevent file bloat." >> "$LOG_FILE" 
fi 

# 2. Fail-Fast Validation: Ensure OpenRGB is actually there before doing anything 
if [ ! -x "$OPENRGB" ]; then 
    echo "$(date '+%Y-%m-%d %H:%M:%S'): CRITICAL ERROR - OpenRGB binary not found or not executable at: $OPENRGB" >> "$LOG_FILE" 
    exit 1 
fi 

# 3. Log the event and attempt to turn lights off using the correct "off" profile 
echo "$(date '+%Y-%m-%d %H:%M:%S'): Initiating sleep sequence - Powersaving LEDs" >> "$LOG_FILE" 
"$OPENRGB" --config "$CONFIG" --profile off 2>> "$LOG_FILE" || "$OPENRGB" --config "$CONFIG" -c 2>> "$LOG_FILE" 

# 4. Wait 3 seconds for motherboard power lines to settle 
sleep 3 

# 5. The kernel scheduler suspends this process context during system sleep 
systemctl suspend 

# ======================================================== 
# SYSTEM RESUMES HERE IF THE USER SESSION SURVIVES 
# ======================================================== 

# 6. Spawn a background loop to handle eventual hardware readiness on wake 
( 
    echo "$(date '+%Y-%m-%d %H:%M:%S'): System awoken - starting hardware polling loop" >> "$LOG_FILE" 
     
    # Poll the USB bus up to 5 times.  
    for i in {1..5}; do 
        if "$OPENRGB" --config "$CONFIG" --profile on 2>> "$LOG_FILE"; then 
            echo "$(date '+%Y-%m-%d %H:%M:%S'): Success - Profile 'on' applied on attempt $i" >> "$LOG_FILE" 
            break 
        fi 
        echo "$(date '+%Y-%m-%d %H:%M:%S'): Attempt $i failed - USB bus unready. Retrying..." >> "$LOG_FILE" 
        sleep 1 
    done 
) & 

# 7. Exit the foreground process cleanly so Steam registers a normal exit 
exit 0 

Strategy 2: Automated Mode

• Who it is for: Users who want a hands-off, "set-and-forget" implementation.
• How it works: It uses a timestamp check (-nt). If the Bazzite Portal updates the main AppImage file, the script automatically identifies it during the next sleep transition. It safely renames your old folder with a unique calendar timestamp backup path (ensuring zero file deletion) and extracts the fresh version completely in the background.

#!/bin/bash 

# --- Configuration Variables --- 
APPIMAGE="/home/gamer/AppImages/openrgb.appimage"
EXTRACTED_DIR="/home/gamer/AppImages/OpenRGB-extracted"
OPENRGB="$EXTRACTED_DIR/AppRun" 
CONFIG="/home/gamer/.config/OpenRGB" 
LOG_FILE="$HOME/openrgb-sleep.log" 

# === Automated Extraction & Update Lifecycle (Non-Destructive) ===
# Triggers if the folder is missing, or if the Portal downloaded a newer AppImage container
if [ -f "$APPIMAGE" ] && { [ ! -f "$OPENRGB" ] || [ "$APPIMAGE" -nt "$OPENRGB" ]; }; then
    echo "$(date '+%Y-%m-%d %H:%M:%S'): Sync Action - New OpenRGB update or initial run detected." >> "$LOG_FILE"
    
    cd /home/gamer/AppImages
    
    # Defensive Architecture: Archive the legacy directory with a unique timestamp instead of deleting
    if [ -d "$EXTRACTED_DIR" ]; then
        TIMESTAMP=$(date '+%Y%m%d_%H%M%S')
        BACKUP_PATH="${EXTRACTED_DIR}_bak_${TIMESTAMP}"
        echo "$(date '+%Y-%m-%d %H:%M:%S'): Archiving legacy directory to: $BACKUP_PATH" >> "$LOG_FILE"
        mv "$EXTRACTED_DIR" "$BACKUP_PATH"
    fi
    
    # Extract the new container seamlessly inside user space
    ./openrgb.appimage --appimage-extract >> "$LOG_FILE" 2>&1
    
    # Rename default extraction directory to match script execution paths
    mv squashfs-root "$EXTRACTED_DIR"
    chmod +x "$OPENRGB"
    
    echo "$(date '+%Y-%m-%d %H:%M:%S'): Sync Action - Update complete. AppRun binary ready." >> "$LOG_FILE"
fi

# 1. Log Rotation: Prevent the log file from growing infinitely 
if [ -f "$LOG_FILE" ] && [ "$(wc -l < "$LOG_FILE")" -gt 500 ]; then 
    # Keep only the last 200 lines of history 
    echo "$(tail -n 200 "$LOG_FILE")" > "$LOG_FILE" 
    echo "$(date '+%Y-%m-%d %H:%M:%S'): Log rotated to prevent file bloat." >> "$LOG_FILE" 
fi 

# 2. Fail-Fast Validation: Ensure OpenRGB is actually there before doing anything 
if [ ! -x "$OPENRGB" ]; then 
    echo "$(date '+%Y-%m-%d %H:%M:%S'): CRITICAL ERROR - OpenRGB binary not found or not executable at: $OPENRGB" >> "$LOG_FILE" 
    exit 1 
fi 

# 3. Log the event and attempt to turn lights off using the correct "off" profile 
echo "$(date '+%Y-%m-%d %H:%M:%S'): Initiating sleep sequence - Powersaving LEDs" >> "$LOG_FILE" 
"$OPENRGB" --config "$CONFIG" --profile off 2>> "$LOG_FILE" || "$OPENRGB" --config "$CONFIG" -c 2>> "$LOG_FILE" 

# 4. Wait 3 seconds for motherboard power lines to settle 
sleep 3 

# 5. The kernel scheduler suspends this process context during system sleep 
systemctl suspend 

# ======================================================== 
# SYSTEM RESUMES HERE IF THE USER SESSION SURVIVES 
# ======================================================== 

# 6. Spawn a background loop to handle eventual hardware readiness on wake 
( 
    echo "$(date '+%Y-%m-%d %H:%M:%S'): System awoken - starting hardware polling loop" >> "$LOG_FILE" 
     
    # Poll the USB bus up to 5 times.  
    for i in {1..5}; do 
        if "$OPENRGB" --config "$CONFIG" --profile on 2>> "$LOG_FILE"; then 
            echo "$(date '+%Y-%m-%d %H:%M:%S'): Success - Profile 'on' applied on attempt $i" >> "$LOG_FILE" 
            break 
        fi 
        echo "$(date '+%Y-%m-%d %H:%M:%S'): Attempt $i failed - USB bus unready. Retrying..." >> "$LOG_FILE" 
        sleep 1 
    done 
) & 

# 7. Exit the foreground process cleanly so Steam registers a normal exit 
exit 0 

Step-by-Step Implementation

Step 1: Save the Script and Grant Permissions

1. Open your terminal (Konsole).
2. Create a new file named openrgb-sleep.sh in a persistent user-space folder (e.g., /home/gamer/openrgb-sleep.sh). Remember to replace gamer with your actual username if it differs.
3. Paste the complete code block of your chosen strategy into the file and save it.
4. Mark the script as executable by running:

   chmod +x /home/gamer/openrgb-sleep.sh
   

Step 2: Initial Extraction (Required for Strategy 1 Only)

If you chose Strategy 1 (Manual Mode), you must manually perform the initial extraction so the script has a target binary to run:

1. In the terminal, navigate to your AppImages folder:

   cd ~/AppImages
   

2. Run the extraction flag:

   ./openrgb.appimage --appimage-extract
   

3. Rename the output folder to match the script's configuration path:

   mv squashfs-root OpenRGB-extracted
   

(Note: If you chose Strategy 2, skip this step entirely. The script handles it automatically on the first run).

Step 3: Add to Steam Game Mode

To trigger this script directly from your Game Mode interface using a controller, add it as a Non-Steam shortcut:

1. Switch to the Bazzite Desktop environment and open the Steam Desktop Client.
2. Click Add a Game (bottom-left corner) -> Add a Non-Steam Game...
3. Click Browse, navigate to your script's folder location, select openrgb-sleep.sh, and click Add Selected Programs.
4. Locate the script in your Steam Library list, right-click it, and select Properties.
5. Change the name to a clean title, such as Sleep System.
6. Return to Game Mode. The script will now be fully operational under the Non-Steam tab in your library.

Verification Logs

To monitor script operations, verify profile application success, or check automated backup folder paths, view the rolling history log at any time by opening the following local file: /home/gamer/openrgb-sleep.log (substituting gamer with your custom username if applicable).

Hi;

First time Bazzite attempter here. I've created a ≈500gb partition as the attached screenshot. But when I reboot into the live installer, I get as far choosing language and keyboard, date and time, and then to the installation method screen...

I click "change destination", select the NVME witb Windows on, choose "share disk with other operating systems" (leaving reclaim space and encrypt data off) and on the following screen I get:

"Warning: your /boot/efi partition is less than 500MiB which is lower than recommended for a normal Bazzite install. Click Next again to proceed despite this warning".

So I'm guessing it's trying to install into the 500Mb Recovery Partition instead of the 500gb empty parition. How do I get it to choose the right one?

Thanks for any (noob-friendly) guidance!