Thank you for helping to keep GamingOnLinux civil and safe!
Please tell us why you're reporting this content. Please note we store your IP address for all reports to help prevent spam and abuse. You can also email any complaints to: [email protected].
- Survive an elevator trying to eat you in co-op horror KLETKA when it releases February 19
- Draft code submitted to KDE Plasma turns it into a full VR desktop
- Proton Experimental brings updates for MonoGame, Rockstar Launcher and more
- Valve tweak Steam AI disclosure form for developers to clarify it's for content consumed by players
- No Rest for the Wicked co-op update lands on January 22 and it hit a big sales milestone
- > See more over 30 days here
- Casual/Social places for developer chatter
- simplyseven - Will you buy the new Steam Frame?
- eev - One-time logout
- Liam Dawe - Away later this week...
- Liam Dawe - Weekend Players' Club 2026-01-16
- grigi - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
On CachyOS:
I was not able to get the Lutris method to work. The installer kept complaining about a file system error and the Battle.net installer would freeze. I attempted this installation many times (~10) and eventually managed to install it without a file system error appearing, but even then, Battle.net would give either the "Battle.net Agent Went to Sleep" error or the "An error occurred while loading game information" error. I tried changing the Runner configuration to many other options than the default, but they all resulted in Battle.net freezing immediately after launch. I didn't try Jiloup's suggestion of using Proton Plus, though, so look at that if you insist on Lutris.
I was able to get the Steam method to work. Use Steam to run the Battle.net setup exe, and then re-target it to the launcher exe that is installed. However, the suggested Compability setting of Proton 9.0-4 still lead to the "Battle.net Agent Went to Sleep". Once I switched it to proton-cachyos-10.0-20251120, that error went away, Battle.net started normally, and I was able to install games. I then tried Proton 10.0-3, which also worked.
TL;DR: I'd recommend the Steam method, and Proton 10.0+