Skip to content

Instantly share code, notes, and snippets.

@fsworld009
Last active July 17, 2025 11:50
Show Gist options
  • Save fsworld009/d9f669b469cea9d9039f1976a5fbbadc to your computer and use it in GitHub Desktop.
Save fsworld009/d9f669b469cea9d9039f1976a5fbbadc to your computer and use it in GitHub Desktop.
Bazzite-DX notes

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment