I just installed unity hub on my ubuntu 22.04 following this guide and installed unity editor 2022.3.9f1. after creating a test project to see it working it recommended me to open it in safe mode because it had compile errors, but i chose to ignore it as the project was just being created. after that the console threw 100 errors all stating something like what the title says, for example:
“Library/ScriptAssemblies/Unity.Mathematics.Editor.pdb: Failed to copy “Library/Bee/artifacts/2400b0aE.dag/post-processed/Unity.Mathematics.Editor.pdb” to “Library/ScriptAssemblies/Unity.Mathematics.Editor.pdb” with cp”
i have no idea whats going on and couldnt find anything regarding this anywhere. can anybody help me? also idk if this is important to add, but i installed unity hub and editor on a second disk as my main disk is an ssd for performance and my second disk is hdd for storage. my only idea would be that it for some reason doesnt have full access to the disk and thus the copies cant be made or something like that but dont take my word for it, just adding it because it might be important but idk
@D4rkMn If you create a project on your primary drive does that error still happen? For the past 3 months or so, I’ve been experiencing the same problem. My work around has been to work primarily on my main drive and move everything over when I’m done. I’ve been trying to find a solution for this since September and I’m hoping you’ve found a better solution since posting this.
Hello, using Unity 2022.3.30f1 on Linux, and I encountered this problem out of a sudden after working with no issues for months. This is really a showstopper. Since I’ve been working with no issues for the past few months, I thought there was something I recently changed that could have influenced the problem. And indeed, the day before I upgraded my Linux kernel, which I confirmed was the culprit. I changed my OS boot configuration to load the previous kernel and the problem was gone.
Below is some more info for the curious, and hopefully, it could shed more light on the matter as I have no idea what exactly was the cause:
My machine is a PC with dual boot - Linux Mint Debian Edition (Faye) and Windows 11. My Unity project resides on an NTFS drive, so I can work on it from both OS-es. The drive resides on the main NVMe SSD disk and is permanently mounted to the Linux OS trough fstab (if that matters).
My working setup: LMDE using Kernel version 6.1.0-21-amd64 (as evident from the command uname -r)
The broken setup: LMDE using Kernel version 6.7.12+bpo-amd64, which I installed from the backports (it is not officially enabled for the current LMDE distribution yet). While I did not experience any issues with the OS, this triggered the problem of this thread. I only am wild guess-ing, but I would blame the NTFS support of the new Kernel, or something related to disk firmware that is changed in the newer kernel, because I have the exact same LMDE setup with this newer kernel on a laptop (the new kernel is really needed there because hardware is new and lacks firmware support in older versions), and the laptop works perfectly with Unity. The only difference from my PC setup, is that the laptop is a single OS machine, so no NTFS drives. Of course, hardware is different too.
I hope this to be of use to someone hitting the problem again. I’d be curious to know what exactly caused this dreaded problem on a far newer Unity version and relatively modern hardware (my PC is about 2 and half years old at the time of writing, the laptop is quite new around the start of 2024).
