Now bottles seems completely broken. Cannot initialize the user environment for a new test user, not even in the environment where the previous roon installation still works for my standard user.
So, bottles is no reliable way to roon on linux either.
Which then, as it works for others (so not update server or general internet related), seems to be networking/communication related (on your end). As your Roon Server could update, it may be just your client machine/installation. It can be a security/antivirus software that blocks access, a firewall issue, issues with name resolution (DNS, hosts file), some network port conflict, a storage issue (no space left, can’t read/write a file) or … You should probably check your machine’s installation thoroughly.
For me it is that I use Roon and Wine (direct or with bottles) since years and on different machines and Roon’s self-updates always worked (unless Roon Labs broke their server {services}).
This works great for both winecfg and regedit. I did set the keys, and ran those utilities with an unset DISPLAY variable. It works. Fonts look sharper. HOWEVER, UNFORTUNATELY, Roon still crashes
I apologize for the late reply, but I would like to respond:
I very much doubt that the machine on which the client installation is running is the problem, as the client and server are running on the same machine. The only difference is that Roonserver is running inside of a Distrobox (with a different hostname), while Roon Client is running in Bottles. They both Connect to the Internet the same way using my host system. I don’t use an Antivirus on my System & only use a firewall for a different user account. Well, in the end, I can solve it manually, so it’s not so bad. Thanks anyway for the friendly advice, ideas & tips.
I am running Roon Server in a Podman container, and Roon client using Wine. Both update via the client (as I don’t enable automatic updates), and this is the experience others have when running Roon on Linux. Therefore, the only rational explanation for the issue is some localized setup issue preventing the client from updating.
This isn’t relevant, as both server and clients download updates independently. The client doesn’t connect to the Internet, except for downloading updates, as it is the server that handles metadata, images etc. So, I’d double-check that the Bottle has Internet capability.
I had been having common issue of crashing after selecting an audio zone but after recent updates Roon client is working for me perfectly now with this configuration:
SYSTEM:
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.9-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
You beautiful person you! I’ve been fighting bottles and roon for days and was just about ready to rip my face off out of frustration. This finally did the trick.
For anyone following in our footsteps:
Runner soda-9.0.1
dxvk.2.3
vkd3d-proton-2.10
I imported the yml file from earlier in this thread. Changed the runner to Soda, added the above to launch options and …tiggityboo!
For volume, look at your device setup. You can set it to device volume, dsp volume or fixed. DSP makes it roon UI controllable.
For example, I usually control my roon via my android phone volume buttons.
If using a linux PC UI, I use a wireless keyboard with volume controls. These work at the linux box level. Same with play, previous/next. Logitech k400r.
Running on Tuxedo OS. For some reason Bottles instantly crashes here. But I was able to install Roon through Lutris. Only had to change the shortcut to include the path to the Roon.exe.
But after that it installed and runs succesfully without any additional tinkering.
For Bazzite users like me (who cannot install the great custom scripts provided on github…): I finally got Roon gui working on Lutris (in the end it was quite simple): In Lutris I installed the roon-installer-exe through wine, setting audio output as alsa (not pulseaudio, didn’t work…) and as DLL-enforcer i set key as “windows.media.mediacontrol” and value as %command% . Then I had to change the location of the exe file to …/drive_c/users//AppData/Local/Roon/ Application/Roon.exe. Everything else was left default as lutris suggested.