@igormpc as a follow up to my last message, you may realise I didn't get very far with the feedforward installation, something funky going on with the build dependencies that is beyond me so I've shelved it for the moment so I can pick lower hanging fruit -
Which will just update SuperDirt to the latest git tag (v1.7.3) and update tidal to the latest available from cabal (1.7.10) without touching any of the supercollider or editor configs.
That's correct, by default I will use the distro packaged supercollider which does link the QT support, if there is a newer version of supercollider already installed then I usually just leave those steps out (iirc).
I assume the failure is because systemd under WSL is probably not running - I don't explicitly offer support for WSL, but it's certainly something I'll consider resolving.
Is your student running the packaged supercollider, or compiled from source?
I also tried the Pulsar version, that worked but I've run into another problem. I had an old broken SC install which I thought I'd blown away but there seems to still be enough remnants on my system (no matter how much I purge remove). ansible-tidalcycles skipped the SC install which I assume is as a result of the old broken install. Might just be time to start from scratch with a fresh OS.
all of that is quite unexpected, it looks like you've removed all of the repositories from your system except for a suse repo (hosting obs maybe?)
Whatever the case, your system is in a very unusual state - a reinstall won't hurt, but if you want to try some stuff:
# re-add your ubuntu repos
sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc) main universe restricted multiverse"
update
sudo apt-get update
check neovim
apt-cache policy neovim
It skips when the version output by sclang -v is newer than what's available in the repos - so make sure the sclang (and associated sc binaries) have also been removed in your clean up
Thanks for your help. Yep, I had to remove some repos because they were no longer being maintained, which was breaking all updates. I find it very difficult to diagnose issues with broken parts of ubuntu, despite having come across these kinds issues fairly frequently over the years. cheers again. I'll let you know how I go.