Mat

As far as I can tell, the error occurs here: https://github.com/nicotine-plus/nicotine-plus/blob/0d341d2d6df325f0891fc52f1e5b6f0f5c7adf5d/pynicotine/transfers.py#L1018-L1028 What is your incomplete downloads folder set to? The path you included in the issue report seems to be...

> setting an actually existing 'incomplete download' folder solved that issue. My bad... Not your fault, the transfers.py file has quite vague error messages that I will replace eventually. >...

Could you check the permissions of the `Soulseek Downloads` folder and any subfolders, and perhaps try downloading an album to another folder somewhere else? `Soulseek Downloads/complete` looks like the folder...

> If the path returned by the environment is not writable, then we should fall back to `legacy_dir` @mathiascode No, the legacy dir should not be used anymore. The root...

> [Errno 30] Read-only file system I suppose you're storing finished downloads on some removable drive? Maybe there's a temporary issue with it that requires unplugging or restarting. Are you...

"run from network drive" Could you expand on this? How is the network drive set up? Running Nicotine+ from a network drive has never been tested before, and it seems...

> To help us figure out if the problem lies within the Nicotine+ executable or if it is related to the Python GObject / Gtk runtime library, perhaps you can...

Relevant code in Nicotine+ is here: https://github.com/nicotine-plus/nicotine-plus/blob/6c1dcd0e8e75ca213922a6304f8aafa59b4e1768/pynicotine/shares.py#L727-L745

My guess is that the multiprocessing module has trouble finding the bundled Python executable for some reason, but I can't say for sure until I've set up a network drive...

Something is wrong with the `sys.executable` path. If I call multiprocessing.set_executable with a random invalid path, I get the same traceback as the original issue.