Arch Linux User Repository

Run $ osu-stable to start osu!

If you see:

WARNING: Executable not found: ~/.local/share/osu-stable/osu!.exe

It means that the osu! installation either was either cancelled or stopped. run $ osu-stable --force-reset and answer Y to the Clear data directory prompt

If osu! is not starting, it's possible your prefix has issues - run $ osu-stable --force-reset and answer Y to the Remove Wine prefix during force-reset? prompt

Package currently fails to build, osu-installer-20260217.exe is failing the integrity check.

in osu.sh (when running osu-stable) if the user doesn't want to use the prefix "marked as incomplete" it will rm -rf $WINEPREFIX without warning or input

    read -rp "⚠️  Wine prefix ${WINEPREFIX} exists but is not marked complete. Use it anyway? [y/N] " ans
    if [[ ${ans:-n} =~ ^[Yy]$ ]]; then
      touch "$COMPLETED_FLAG"
      echo "✅ Marked existing prefix as completed."
    else
      echo "🧹 Removing existing Wine prefix at $WINEPREFIX..."
      rm -rf "$WINEPREFIX"
      setup_wineprefix
    fi

whether the prefix is "marked as incomplete", is determined by the bash expression "[[ -f $COMPLETED_FLAG ]]" which depends on COMPLETED_FLAG="$WINEPREFIX/.completed"

so if $WINEPREFIX, doesn't contain a .completed file, it can rm -rf the environment variable without notifying the user it will

This behavior is standard for this package since 6d20dd24d5ae

Checksum is not updated, validity for osu-installer-20251128.exe fails on my end.

As of January 2, 2026, the checksum for osu-installer-20251128.exe is 69f7cf0a210661d6a7888f14316508fd2e9d2e56b78bc09ba76e6c86aa5cf9d8

Checksum is somehow broken again:

391e35501c1e9875bacc07cb9c70185e70f72b3bfde1a0dc57b8a2b4c461008e  osu-installer-20251128.exe

updated - some CI issue on my end I haven't been able to diagnose

Somehow the checksums for osu-installer-20251102.exe do not seem to match for me, my checksum is 47c8718333183100051d4aacd6428d54ebfe0821d18dd707cedb073c01008674

This package is currently broken from what I can tell. Starting it yields this:

▶ osu! (20250815 → 20250815). Up-to-date…
INFO: umu-launcher version 1.2.9 (3.13.7 (main, Aug 15 2025, 12:34:02) [GCC 15.2.1 20250813])
INFO: No GAMEID set, using umu-default
INFO: steamrt3 is up to date
INFO: UMU-Proton is up to date
WARNING: Executable not found: /home/myuser/.local/share/osu-stable/osu!.exe
ProtonFixes[49732] WARN: [CONFIG]: Parent directory "/home/myuser/.config/protonfixes" does not exist. Abort.
ProtonFixes[49732] INFO: Running protonfixes on "UMU-Proton-9.0-4e", build at 2025-05-04 02:12:42+00:00.
ProtonFixes[49732] INFO: Running checks
ProtonFixes[49732] INFO: All checks successful
ProtonFixes[49732] WARN: Game title not found in CSV
ProtonFixes[49732] INFO: Non-steam game UNKNOWN (umu-default)
ProtonFixes[49732] INFO: No store specified, using UMU database
ProtonFixes[49732] INFO: Using global defaults for UNKNOWN (umu-default)
ProtonFixes[49732] INFO: Non-steam game UNKNOWN (umu-default)
ProtonFixes[49732] INFO: No store specified, using UMU database
ProtonFixes[49732] INFO: No global protonfix found for UNKNOWN (umu-default)
Proton: /home/myuser/.local/share/osu-stable/osu!.exe
Proton: Executable a unix path, launching with /unix option.
wine: using kernel write watches, use_kernel_writewatch 1.
fsync: up and running.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Success.

If you run it with --force-reset it works and launches after you remove/reinstall everything and then fails to launch again on the next run without --force-reset.

From what I can tell the issue is the installer installs osu!.exe into: /home/myuser/.local/share/wineprefixes/osu-stable/drive_c/users/steamuser/AppData/Local/osu!/osu!.exe and not where OSU_STABLE_DATA_DIRECTORY is located

@Xbz: I'm sorry, but I can't reproduce your error at all - using osu-stable --force-reset and answering 'y' to both prompts should result in a working game. The restart osu prompt from the game should only appear when osu is trying to update and is a quirk I haven't been able to solve - but doesn't seem to cause any issues at all in my testing.

Can you confirm you have the following output?

$ pacman -Q lib32-gnutls lib32-gst-plugins-base-libs lib32-libxcomposite umu-launcher icoutils pipewire-pulse
lib32-gnutls 3.8.10-1
lib32-gst-plugins-base-libs 1.26.6-2
lib32-libxcomposite 0.4.6-2
umu-launcher 1.2.9-1
icoutils 0.32.3-3
pipewire-pulse 1:1.4.8-2

@envolution you here?

I am getting "System.Exception: Executable filename is not correct! " any idea ?