osu! builds from the Stable release stream.
Stable is the most recent version of osu! that is not on test phase. It currently renders through OpenGL 3.x, that allows Wine to get the same performance as on Windows. It needs .NET Framework 4.5+ to work.
There are also Beta and Cutting edge release streams that allow to test the latest development features. However they change frecuently and older versions of them get rapidly obsolete. Its compatibility level on Wine is currently the same as Stable.
Single player (osu! gamemode)
What does not
What was not tested
Multiplayer, Shader Effects
Taiko, osu!mania, Catch the Beat gamemodes
Much worse performance than in Windows (less than 50% FPS I guess, but it's maybe because of my Intel GMA 4500 MHD "GPU") and it's somehow more laggy. It was necessery to install dotnet20 and xna31
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Aug 02 2019||4.0.1||Yes||Yes||Yes||Gold||Yuki Snowy|
|Show||Arch Linux x86_64||Apr 04 2019||4.5||No, but has workaround||Yes||Yes||Gold||Yudha|
|Show||Solus||May 09 2019||4.1||Yes||Yes||No||Silver||Ivan Pavluk|
|Show||Ubuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)||Oct 20 2018||3.18-staging||Yes||Yes||Yes||Gold||Pham Truong Thanh Trung|
|Show||Ubuntu 18.10 "Cosmic" amd64 (+variants like Kubuntu)||Nov 17 2018||3.0.3||Yes||Yes||Yes||Silver||CONBlaze|
Last update: 2019-05-03.
This section describes some minimum steps required to run osu! in vanilla Wine. Other sections have additional information to improve user experience. For practical purposes, winetricks is used (it's not mandatory since you can install .NET Framework manually but it requires more steps), so first get the latest version:
$ wget 'https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks'
$ chmod +x ~/winetricks
1) Create a new 32-bit Wine prefix:
$ env WINEARCH=win32 WINEPREFIX=$HOME/.wineosu wineboot --init
If Wine prompts for installing Mono, click Cancel.
2) Install .NET Framework 4.5:
$ env WINEPREFIX=$HOME/.wineosu ~/winetricks dotnet45
3) Download and install osu!:
$ mkdir 'osu!'
$ wget '
BUG 44184: If the installer stuck in an endless loop, close it and then:
This will create a dummy discord-rpc.dll and try to start osu! again.
4) Creating a shortcut:
Create a new plain text file and put the following:
Save this file as osu!.desktop in ~/.local/share/applications and mark it as executable:
Take the path to an osu! logo image and put it in the Icon field if you want to set an icon for the shortcut.
Last update: 2019-08-21.
Arch Linux specific:
osu! doesn't render anything on screen and exits with some X server error message: install lib32-libxcomposite package:
$ sudo pacman -S lib32-libxcomposite
osu! can't connect to internet: install lib32-gnutls package:
$ sudo pacman -S lib32-gnutls
Japanese characters no displaying correctly: install MS Meiryo font:
$ env WINEPREFIX=$HOME/.wineosu ~/winetricks meiryo
Note that korean characters are not shown with this font.
Options menu symbols and audio controls are missing: install GDI+:
$ env WINEPREFIX=$HOME/.wineosu ~/winetricks gdiplus
GDI+ installer is a ~538MB file. If your internet connection is slow or very limited, consider instead taking a copy of gdiplus.dll from a Windows 7 installation and copying it to your Wine prefix, and then add manually a Native override for gdiplus.
$ env WINEPREFIX=$HOME/.wineosu winecfg
Go to Libraries tab, add gdiplus and set it to Native Then Builtin. Close all dialogs by clicking OK.
Other known problems:
$ pkill osu
Press Ctrl+Alt+F7 (or Ctrl+Alt+F1 on some systems) to return to your desktop environment.
Please leave us a comment in Comments section below if you still have problems installing or running osu!.
Last update: 2019-01-07.
When filling a Test Result report, mention at least the exact osu! build number you tested. It can be found inside the game just at the end of the Options menu. It usually looks like b20171106.5 or 2017.1030.0. It can also be found on "osu!.«user».cfg" file (find the LastVersion value).
Remember to follow the Installation guide, step by step, before considering that you've failed to get osu! running. This is important because the guide has been designed to work for any system. Also mention whatever you did in order to get osu! working, regardless it is on the Installation guide or not.
For more information about how to fill a report, see AppDB Test Results Guidelines.
If osu! doesnt't recognize internet connection and you have internet connection, install 32-Bit GNUTLS Package. In Arch Linux,
sudo pacman -S lib32-gnutls