UB
Universal Blue•11h ago
panachemidi

Can't attach Rider debugger to Unity

My setup: bazzite:stable, up to date (i also tried bazzite-dx:stable) Rider 2025.2.2, installed through Jetbrains Toolbox, itself installed through ujust install-jetbrains-toolbox Unity 6000.0.30f1, installed through the Unity Hub flatpak Both Rider's and Unity's plugins are up to date in my project. The problem: Whenever I try to attach to Unity from Rider, the debugger agent fails to connect. I get a popup saying 
Unable to connect to Unity Editor
Please follow ''Debug in the Unity Editor'' documentation.
Unable to connect to Unity Editor
Please follow ''Debug in the Unity Editor'' documentation.
which doesn't help. The idea.log shows: 
2025-09-23 17:20:56,707 [4067631]   WARN - #c.j.r.d.DebuggerWorkerProcessHandler - Debugger.Worker process was terminated before the debug session was initialized. Exit code: 0. Output: 
/var/home/****/.local/share/JetBrains/Toolbox/apps/rider/lib/ReSharperHost/linux-x64/JetBrains.Debugger.Worker --runtimeconfig /var/home/****/.local/share/JetBrains/Toolbox/apps/rider/lib/ReSharperHost/JetBrains.Debugger.Worker.runtimeconfig.json --mode=client --frontend-port=43281 --plugins=/var/home/****/.local/share/JetBrains/Toolbox/apps/rider/plugins/rider-godot/dotnetDebuggerWorker;/var/home/****/.local/share/JetBrains/Toolbox/apps/rider/plugins/rider-unity/dotnetDebuggerWorker
2025-09-23 17:20:56,707 [4067631]   WARN - #c.j.r.d.DebuggerWorkerProcessHandler - Debugger.Worker process was terminated before the debug session was initialized. Exit code: 0. Output: 
/var/home/****/.local/share/JetBrains/Toolbox/apps/rider/lib/ReSharperHost/linux-x64/JetBrains.Debugger.Worker --runtimeconfig /var/home/****/.local/share/JetBrains/Toolbox/apps/rider/lib/ReSharperHost/JetBrains.Debugger.Worker.runtimeconfig.json --mode=client --frontend-port=43281 --plugins=/var/home/****/.local/share/JetBrains/Toolbox/apps/rider/plugins/rider-godot/dotnetDebuggerWorker;/var/home/****/.local/share/JetBrains/Toolbox/apps/rider/plugins/rider-unity/dotnetDebuggerWorker
What I tried: My guess is that Unity Hub needs additional permissions in flatpak, but I've tried some stuff and it didn't fix it. I tried allowing socket-session-bus, socket-system-bus, device-dri && device-input (which I figure I'd need anyway), device-shm, allow-devel, and access to /dev. No dice. Did someone figure this out?
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?