Steps to Reproduce:
Install terminal quit with output: bash: line 54: ldconfig: command not found
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: N/A
I have the exact same issue.
I was using the Insiders version of SSH-Remote for the Raspbian support, but have just read that the Non-Insider version now supports it.
I have switched to the release SSH-Remote and it works like a charm.
Just started getting this same exact issue today, one two different computers, one is running windows and the other is OS X. I cannot switch to the release version because I need to use it with a raspberry pi. This has totally broken my dev environment
How can someone roll back to 2019.9.28260?
Same issue here, on numerous (previously ) known-working RPIs. exact same error as op.
How can someone roll back to 2019.9.28260?
I figured it out, if you right click on the extension in Vscode, you can select a previous version to use
Good Tip @tenkaisynapse I ended up using the stable version as @wil19558 suggested. Either way there is an issue with the current nightly build, as least as it relates to the RPI.
btw in case it's useful (to the devs): the user configured to login with vscode has access to ldconfig (it's location is in PATH and command is executable) when logging in with that user via SSH (outside vsc).
btw in case it's useful (to the devs): the user configured to login with vscode has access to ldconfig (it's location is in PATH and command is executable) when logging in with that user via SSH (outside vsc).
Agreed, when I log in via SSH, i have access to ldconfig as well.
Same issue while trying to connect to a Debian.Buster.
The install script is looking for ldconfig but ldconfig can only be executed by root, not by a normal user. (ldconfig needs privileges to do some actions, like creating the temporary file cache.)
// @joaomoreno do you have this setup and can reproduce it on insiders?
I just hit this last night on my RPi 4 as well, I assumed it was a 4 issue, but it seems not.
Sorry! So the raspberry pi has ldconfig available, you just need to be root? Is that the case for everyone or is the PATH wrong in the install script? I wouldn't expect to see command not found if you just need privileges.
Pushed an improvement for this, not 100% sure whether it will fix it or not, please somebody let me know.
The 2019.9.34260 version fixes my issue. Thx.
Yup all good in today's Insiders @roblourens! Thanks!
Connected without issue here as well, Thanks! @roblourens
Most helpful comment
I have the exact same issue.
I was using the Insiders version of SSH-Remote for the Raspbian support, but have just read that the Non-Insider version now supports it.
I have switched to the release SSH-Remote and it works like a charm.