Constant "Error Watching" warnings in console and broken working directory behaviour

Unity
1

Hello there.

I have very recently installed version 2.03 of FMOD Studio and version 2.03 of the Unity integration package on my linux mint machine. Everything seems to work fine (parameter changes, events etc), except for similar and repeating warnings (the only difference between them is that the paths mentioned change) that keep appearing in the console.

The following is one of the warnings:

Error watching /home/[directories leading to root project folder]/[root project folder]/Library/PackageCache/com.unity.shadergraph@ba64c3eae297/Samples~/Common/Subgraphs/Assets/Audio/Music/Desktop: The directory name ā€˜/home/[directories leading to root project folder]/[root project folder]/Library/PackageCache/com.unity.shadergraph@ba64c3eae297/Samples~/Common/Subgraphs/Assets/Audio/Music/Desktopā€™ does not exist.
Parameter name: Path
UnityEngine.Debug:LogWarningFormat (string,object)
FMODUnity.RuntimeUtils:DebugLogWarningFormat (string,object) (at Assets/Plugins/FMOD/src/RuntimeUtils.cs:588)
FMODUnity.BankRefresher:UpdateFileWatcherPath () (at Assets/Plugins/FMOD/src/Editor/BankRefresher.cs:81)
FMODUnity.BankRefresher:Update () (at Assets/Plugins/FMOD/src/Editor/BankRefresher.cs:44)
UnityEditor.EditorApplication:Internal_CallUpdateFunctions () (at /home/bokken/build/output/unity/unity/Editor/Mono/EditorApplication.cs:401)

TL;DR (At least from my understanding): The Bank Import Refresher, instead of using the project root as the starting point for the relative path provided in Build Path, instead goes into a random folder inside the project and uses that as the root for it.

Another, more concerning problem which i suspect may be related to the first, are the frequent ā€œCurrent working directory was changedā€ fatal errors that have started appearing since adding the FMOD integration. I couldnā€™t copy the message but it follows the same pattern as the issue above, i.e the working path being changed to nonsense, forcing unity to shut down to prevent damage.

While the first issue could technically be ignored, as it is just warnings in a console, the second one actually breaks the project, as I keep getting worrying warning windows like ā€œThe scene has been changed, would you like to refresh?ā€ when I havenā€™t touched the scene at all, as well as version control telling me that folders I havenā€™t touched have been changed. I have already done one rollback to be safe.

P.S: I use the Unity Version Control package for version control if it helps.

2

UPDATE: For anyone having this problem in the future, using the Unity Version Control package on Linux is what causes the problem. Since I removed it, there have been no issues. You can still use Unity Version Control without the built-in package with the standalone Plastic SCM application that Unity provides. Good luck!