Bazzite-DX notes

Bazzite-deck-DX.md

Installed on FW13.

2025/08/04 deck-dx variations removed

Note that https://github.com/ublue-os/bazzite-dx/pull/111/files has removed this variation, so rebased on bazzite-dx instead.

Based on description, users are expected to manually login to game mode via SDDM in bazzite-dx variation.

However, after rebasing, it still boots to game mode automatically and behaves like deck images (switch to desktop, return to game mode doesn't require password).

On my FW16, regular SDDM login flow is presented instead. This is most likely caused by rebase history

bazzite-deck -> bazzite-deck-dx 0> bazzite-dx

So the sddm configs for deck variants still presented in /etc/sddm.conf and /etc/sddm.conf.d.

Ideally this can be fixed by cloning SDDM configs from other installations.

But I prefer the current deck behavior so will keep them for now.

2025/07/17 Cannot install with luks enabled

ublue-os/bazzite#2924

Workaround: download image from https://archive.org/details/bazzite-deck

This is a very old build from Apr.2024 but doesn't have this bug and can be installed properly with luks enabled.

Cons: the SSH key in this image has been invalidated, so

1. enroll TPM key would fail, need to disable secure boot for the first boot (be aware that this might enforce entering bitlocker recovery code in your Windows partition)
2. cannot update system

So disable secure boot for the first boot, then follow https://universal-blue.discourse.group/t/important-announcement-regarding-system-updates-action-needed/2689 to do key refresh and system updage:

# If the URL is dead we could curl source instead: `https://raw.githubusercontent.com/ublue-os/config/main/scripts/fix-key-and-update.sh`
curl -sL https://fix.universal-blue.org/ | sudo bash 

Reboot to the updated system then follow https://docs.bazzite.gg/General/Installation_Guide/secure_boot/#method-b-after-installation-method to enroll TPM key and enable secure boot

Another workaround: https://universal-blue.discourse.group/t/installer-crashed-when-enabling-luks-during-manual-disk-partition/9765/3?u=fsworld009 (I don't understand how to perform the steps he mentions)

Boot to desktop

(Only valid when using sddm configs from bazzite-deck for boot to game mode by default)

First make sure bazzite-autologin service is enabled:

systemctl status bazzite-autologin
# if it's not enabled
systemctl enable bazzite-autologin

bazzite-autologin.service would run /usr/bin/bazzite-autologin to delete zz-steamos-autologin.conf and set which session to login on boot.

The zz-steamos-autologin.conf config is used to switch between game mode and desktop mode when clicking "Return to game mode" and "Switch to Desktop Mode":

1. Create the file and set session
2. Logout current session
3. Since Relogin=true is configured, it would automatically login to the chosen session stated in zz- file.

Based on the script, we can create this file so the script will creeate a config file to login to desktop mode on boot:

sudo touch /etc/bazzite/desktop_autologin

Alternative method is to override with yy- configs so it overrides steamos.conf but not zz- for switching modes: https://www.reddit.com/r/Bazzite/comments/1ddwucj/comment/l9ae5c9/

No login password asked when booting, but it's fine for me since I have luks encryption enabled.

disable autologin

sudo vim /etc/sddm.conf.d/zz-steamos-autologin.conf

and comment out [AutoLogin] session.

This is useful to be used together with default to desktop, prompt pw on boot to prevent unauthed access. Although this makes "Returning to Game mode" a simple logout, you need to manually change login session back in SDDM in order to enter gaming mode.

2025/08/04 Random gpu freeze in game mode

journalctl error

 amdgpu 0000:c1:00.0: [drm] *ERROR* [CRTC:93:crtc-0] flip_done timed out

Might be kernel regression

• https://community.frame.work/t/fw13-amd-ui-freeze/64555/5
• https://gitlab.freedesktop.org/drm/amd/-/issues/4238

Bazzite-DX.md

Installed on Framework 16

Installation

Currently There's no standalone image, need to install bazzite first then rebase:

pm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-dx:stable

Most of the configuration steps from Bazzite and Aurora DX note would work. This note only documents things that specific to Bazzite-DX

Lutris

Native and Flatpak lutris coexist

There's issue with native version: lutris/lutris#6146

We can install Flatpak Lutris as fallback, but the shortcut would replace the native one.

To have both in applications menu, we can manually recreate them in ~/.local/share/applications and give them different names:

cp /usr/share/applications/net.lutris.Lutris.desktop ~/.local/share/applications
cp /var/lib/flatpak/app/net.lutris.Lutris/current/active/export/share/applications/net.lutris.Lutris.desktop ~/.local/share/applications/net.lutris.Lutris.flatpak.desktop

2025/07/17

The controller issue was caused by Framework 16 keyboard being identified as joystick https://community.frame.work/t/keyboard-numpad-system-control-appearing-as-game-controller/70326/2

Follow above post to remove it from joystick list fixed the issue.

Legacy Wine-GE versions

Nowadays Lutris has integrated umu-launcher and can simply use Proton versions from Steam. New prefixes should try to utilize GE-Proton Wine-GE has been removed from ProtonUp-Qt, but if they are still required, we could manually download them and put in ~/.local/share/lutris/runners/wine/ (Native) or .var/app/net.lutris.Lutris/data/lutris/runners/wine/ (Flatpak)

linuxbrew path issue

ublue-os/bazzite#2690

fcitx not available

Similar to previous Line installation attemps, some games might not be able to use fcitx, this can be resolved by launching Lutris with XMODIFIERS=@im=fcitx

For above both issues, we can fix it by patching env vars in desktop file:

Modify /home/fsworld009/.local/share/applications/net.lutris.Lutris.desktop and patch fcitx and

Exec=env XMODIFIERS=@im=fcitx PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python PATH="/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin:$PATH" lutris %U

Dev env

Follow Aurora DX guide, but need to install hack-nerd and starship via brew.

Handheld Daemon not working in game mode

https://www.answeroverflow.com/m/1228816116768440442

sudo systemctl enable --now hhd@$(whoami)
# reboot to take effect

Keyboard shortcut doesn't work, ongoing issue ublue-os/bazzite#2923

Backup Audio CD

Method 1: Create bin/cue, then split autio

brew install cdrdao bchunk
# Convert CD into bin+toc
cdrdao read-cd --driver generic-mmc:0x20000 --read-raw --datafile cdimage.bin --device /dev/sr0 cdimage.toc
# Generate cue
toc2cue cdimage.toc cdimage.cue
# Split bin into individual wav tracks based on cue
bchunk -w cdimage.bin cdimage.cue track

The --driver flag might depend on what DVD drive you are using. For me I have to add that, so that the created bin/cue can be mounted by CDEmu and played by VLC properly. Without the flag the bin contains only white noise. Although in this case we could add -s to bchunk command to still get the correct wavs.

Method 2: Convert to single flac + cue for tracks

Need abcde but it's not maintained in linuxbrew, so need distrobox

sudo dnf install abcde flac

Edit ~/.abcde.conf:

# Use built in util to bypass `mkcue not found` error
MKCUE=abcde.mkcue

Convert:

abcde -1 -o flac -a default,cue
# Follow instruction to add title / track / artist, or edit it later

The converted cue file doesn't have correct flac file path, need manual fix. After that you could mount this by CDEmu or open cue in VLC.

To split single flac to multiple files:

sudo dnf install shntool
shnsplit -f "Input.cue" -t "%n %t" "Input.flac" 

KDE dolphin shows incorrect audio title when opening Audio CD

1. Settings -> Multimedia -> CDDB Retrieval, disable all lookups
2. Remove cache: ~/.cddb

VLC

This is because album name is written as title in the flac file (as Vorbis tag). Can use Kid3 from flatpak to remove it. TODO: See if there's option to disable Vorbis tag creation.

Flatpak / Bazzar stuck on installation 100%

Not sure if these actually works..

sudo pkill -9 -f bazaar sudo pkill -9 -f flatpak-system-helper sudo systemctl restart flatpak-system-helper.service sudo rm -f /var/lib/flatpak/.changed run flatpak repair