[SOLVED] problem with external script editor linux mint 21.3 unity 202.3.30f1

Unity Engine
, ,
1

I have some problems with unity and rider on linux mint, both unity and rider are installed as flatpaks.
The first problem I found a work around for (but still I would like it to work like normal) when choosing an external script editor in unity it only shows vscode even though rider is installed. When I try to go to the rider directory:
/var/lib/flatpak/app/com.jetbrains.Rider/x86_64/stable/66a9396cb2e28fe1f47df845ca972b6a269cd373e1a8acd8a019b68c6a7e9895/files/extra/rider/bin/rider.sh I can’t get any further then var, the lib directory just doesn’t show even when showing hidden files. I eventually selected a text file with the file path in it and this worked.

The second and most important problem I have is when opening any script I get a rider prompt asking to open the .sln but its asking it every time I open a script.
In the rider settings under File Types > Recognized File Types I added .sln as new file type and left all the settings blank.

The last problem I have is when I open a script I get these two errors in the console:
Exception thrown while invoking [OnOpenAssetAttribute] method 'Unity.CodeEditor.CodeEditor:OnOpenAsset (int,int,int)' : Win32Exception: Access deniedand

Win32Exception: Access deniedthis is what I get when using ls -l on the scripts: -rw-r–r–

using:
JetBrains Rider 2024.1.2
Unity (2022.3.30f1) LTS
System Info:
Kernel: 5.15.0-107-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy

I know this is a lot but I would really apreciate help.

2

Do you have the Rider package installed in your Unity project?

Unity doesn’t locate Rider by itself, the package is doing it (same with the VS Code package). The Rider package uses a library called RiderPathLocator to find your Rider executable. I think all the issues you describe are happening because RiderPathLocator doesn’t locate the flatpack install. It could be because RiderPathLocator doesn’t support flatpak, or it could be because you installed Unity with flatpak preventing it from accessing the totality of the file system.

If I were you I would first try to install Unity using the officially supported crappy package method. The Unity flatpak is not official and not made by Unity. This is sad and stupid, and I have been complaining about it over and over again, but Unity doesn’t seem to want to use modern distribution method such as flatpak, snap or appimage. But the crappy package install should work just fine on Linux Mint.

If, after this, Unity still can’t find Rider then I would try installing Rider through the Jet Brains Toolbox app. Again, the Rider flapak is not official and not supported by Jet Brains. Snap is another option since the Rider snap is official.

If it turns out that installing Rider using something else than flatpak solves the issue then I think you should consider reporting a bug to RiderPathLocator. There is no reason it shouldn’t find the flatpak install. You should check this topic where I discuss another issue regarding RiderPathLocator. They are open to bug reports.

Hope this help.

1 Like
3

THANK YOU SO MUCHH!!! :smile: Installing it the official way fixed everything! I thought everything in the software manager was official, apparently not.

(how do I mark a thread as solved?)

4

Click the Thread Tools button at the top of the thread (only you can see it) and change the tag in the title.

1 Like