Release 1.1.4

• fix zipapp build losing permissions in artifact build
• fix field command in snap
• fix runtime path in snap
• feature: supporet running native linux executables with umu
• add fedora 41 build
• fix cloud save issue in heroic

Release 1.1.3

• Fixed issue that prevented heroic and lutris from using UMU as a game installer instead of wine
• Fixed issue where sometimes DISPLAY envvar would get lost between handoff from umu to pressure vessel
• Refactor/cleanup of window management code under gamescope -- both lutris and heroic can fully install and run games inside gamescope while both inside or outside of flatpak now.
• Winetricks is now fully useable through UMU and GE-Proton/UMU-Proton
• Updated apparmor bwrap permission profile to recommendations from upstream apparmor folks
• Added a basic shim script to allow performing modifications inside the pressure vessel container after UMU handoff has happened.
• Cleaned up standalone flatpak script to prepare for submission upstream
• Fixed a few places that needed lock files in place to prevent prefix corruption if multiple instances are running
• Missing 32 bit dependencies added for Nix packaging

Notes:

• We're still working out github task attachments for releases being automated. For now we're manually attaching from the latest 1.1.3 builds in the actions section. Thanks for baring with us.

• A refactor was submitted to Lutris to allow full UMU functionality on the lutris side:
  lutris/lutris@3a45272

• Lutris and Heroic also should be receiving the permissions they need in flatpak soon if not already:
  flathub-infra/flatpak-builder-lint@7aa2300

Release 1.1.2

• Fixes some issues with runtime installation when transitioning from RC4 to 1.1.1+ #222
• Fixes some flatpak related environment variable parsing #221
• Fixes debian dependencies in .deb build files (requires Debian 12 or higher) #216
• Fixes invalid cross-link device issue #219
• Fixes 'None of the supported CPU architectures are common to the graphics provider and the container (tried: x86_64-linux-gnu, i386-linux-gnu)' error #213
• Added apparmor bwrap permissions profile #210

Release 1.1.1

First official release of UMU launcher!

• Should work inside both flatpak and snap

We do not have official builds for flatpak or snap yet, but instructions are provided on building and using for both:

https://github.com/Open-Wine-Components/umu-launcher/tree/main/packaging/flatpak
https://github.com/Open-Wine-Components/umu-launcher/tree/main/packaging/snap

0.1-RC4

Instruction for installing via dnf:

Install:

sudo dnf install -y  umu-launcher*.rpm

Remove

sudo dnf remove -y umu-launcher

Usage examples:

winecfg:

GAMEID=umu-starcitizen WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen umu-run winecfg

running a game using the default latest UMU-Proton:

GAMEID=umu-starcitizen WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen umu-run  /path/to/some/game.exe

running a game using the latest GE-Proton:

GAMEID=umu-starcitizen WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen PROTONPATH=GE-Proton umu-run /path/to/some/game.exe

running a game using a specific proton version:

GAMEID=umu-starcitizen WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen PROTONPATH=GE-Proton9-1 umu-run /path/to/some/game.exe

Instructions for installing flatpak via test tarball:

Install:

tar -xf umu-flatpak-test.tar.gzV
flatpak --user remote-add --no-gpg-verify umu-repo umu-repo
flatpak --user install umu-repo org.openwinecomponents.umu.umu-launcher

Remove

flatpak --user remove umu-launcher
flatpak --user remote-delete umu-repo

Flatpak usage examples:

winecfg:

flatpak run --env=GAMEID=umu-starcitizen --env=WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen org.openwinecomponents.umu.umu-launcher winecfg

running a game using the default latest UMU-Proton:

flatpak run --env=GAMEID=umu-starcitizen --env=WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen org.openwinecomponents.umu.umu-launcher /path/to/some/game.exe

running a game using the latest GE-Proton:

flatpak run --env=GAMEID=umu-starcitizen --env=WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen org.openwinecomponents.umu.umu-launcher --env=PROTONPATH=GE-Proton /path/to/some/game.exe

running a game using a specific proton version:

flatpak run --env=GAMEID=umu-starcitizen --env=WINEPREFIX=/home/tcrider/Games/umu/umu-starcitizen org.openwinecomponents.umu.umu-launcher --env=PROTONPATH=GE-Proton9-1 /path/to/some/game.exe

0.1-RC3

Testing
-converted ulwgl-run to posix
-added flatpak test tarball

Instructions for installing flatpak via test tarball:

tar -xf ulwgl-flatpak-test.tar.gz
flatpak --user remote-add --no-gpg-verify ulwgl-repo ulwgl-repo
flatpak --user install ulwgl-repo org.openwinecomponents.ulwgl.launcher

Usage example:

winecfg:

flatpak run --env=GAMEID=ulwgl-roblox --env=WINEPREFIX=/home/tcrider/Games/roblox/ org.openwinecomponents.ulwgl.launcher winecfg

running a game:

flatpak run --env=GAMEID=ulwgl-roblox --env=WINEPREFIX=/home/tcrider/Games/roblox/ org.openwinecomponents.ulwgl.launcher /path/to/some/game.exe

For GAMEID check here if one exists for your game:
https://ulwgl.openwinecomponents.org/

If the game runs with nothing needed then no fixes are required and you can use whatever you want for the GAMEID. The GAMEID is the ULWGL_ID used for applying protonfixes from our database.

0.1-RC2

Testing

0.1-RC1

Testing