vscode remote + net install tool = TimeoutSudoProcessSpawnerError

[bqcrabtree]

Describe the bug.

When using the remote-ssh plugin (v0.113.1), .NET Install Tool (v2.1.5), CLIENT OS Kubuntu 24.04 and HOST OS Ubuntu 22.04.2LTS, and attempting to use the command palette (ctrl+shift+p) to install the .NET SDK via either of the install options (global or "new"), the installation fails with the following error.

user requested to download the .NET SDK.
Downloading .NET version(s) 8.0.108-global~x64 ...Repairing .NET Packages for 8.0.108.:
........................................................................................................................................................................................................
Error : (TimeoutSudoProcessSpawnerError)
Failed to download .NET 8.0.108-global~x64:
We are unable to spawn the process to run commands under sudo for installing .NET.
Process Directory: /home/blain/.vscode-server/extensions/ms-dotnettools.vscode-dotnet-runtime-2.1.5/dist/install scripts failed with error mode: true.
It had previously spawned: true.

Reproduction Steps

1. Press ctrl+shift+p to open the command palette
2. Select one of:
   • .NET: Install New .NET SDK
   • .NET Install Tool: Install the .NET SDK System-Wide
3. Wait for a while for the SDK download to fail
4. Receive the above error

Expected Behavior

The .NET SDK should be installed, or an error message with corrective steps or a link to corrective steps should be displayed.

Exceptions & Errors (if any)

TimeoutSudoProcessSpawnerError
"We are unable to spawn the process to run commands under sudo for installing .NET."

.NET Install Tool Version

v2.1.5

Your operating system? Please provide more detail, such as the version and or distro above.

Client/local OS: Kubuntu 24.04 (Ubuntu with KDE Plasma 5)
Host/remote OS: Ubuntu 22.04.2 LTS

VS Code Version

1.92.2

[bqcrabtree]

This may not be a bug, but I've been unable to find corrective steps via searches for the error name or error message. If this isn't a bug and is expected behavior, a workaround or other documentation would be very helpful.

[nagilson]

Thank you for this report. If you may upload the log that's requested in the issue form, that would help us diagnose it better.

This situation is interesting in that it looks like the sudo process had spawned before hand and it failed to launch again. If you reboot the underlying system you're remoting into, I would expect it to work?

Based on the messages you also have the .NET SDK installed correctly anyways, though it may not be completely up to date.