Can't get the new Extension to run

Technical Support
, , , ,
1

I get this error in the .apollox.cmd.log when starting VSC in my directory:
The xonsh in /usr/bin/xonsh is not linked to /home/steve/.local/share/pipx/venvs/xonsh/bin/xonsh, trying to relink …

Insufficient permissions to create /usr/bin/xonsh and PSSWD is not set.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I can help you troubleshoot this Torizon IDE Extension error. Before providing specific solutions, I need to understand your setup better.

Setup Information Needed

Could you please provide the following details:

  • Operating System: Which OS are you running (e.g., Ubuntu 20.04, Ubuntu 22.04, etc.)?
  • Hardware: Which Toradex hardware are you working with (e.g., Verdin iMX8M Plus, Verdin AM62, Apalis iMX8QP, etc.)?
  • Torizon OS Version: What version of Torizon OS are you running on your device?

You can get detailed information about your hardware and OS by running the tdx-info command on your device. More details are available at: Getting Device Information with Tdx-Info | Toradex Developer Center

Initial Observations

The error you’re encountering appears to be related to xonsh (a Python-based shell) permissions during the extension’s dependency installation process(1). The extension attempts to install necessary dependencies during first activation and may require sudo privileges(1).

Immediate Steps to Try

  1. Check Terminal Focus: During extension activation, ensure you’re watching the TERMINAL tab in VS Code, as other extensions might move focus away from pending installation requests(1).

  2. Verify Docker Installation: Make sure you have Docker Engine properly installed (not Docker Desktop, which isn’t officially supported)(1).

  3. Check VS Code Installation Method: Ensure VS Code wasn’t installed via Snap or Flatpak, as the IDE Extension won’t work with those installation methods(1).

Once you provide your platform details, I can give you more targeted troubleshooting steps for your specific setup.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

I am running VSCode in WSL, Ubuntu 24.04. This worked fine yesterday.
Here is the log:
04-30 11:06:38.993] Activating Torizon IDE …

[04-30 11:06:38.993] Torizon IDE version :: 3.3.0

[04-30 11:06:39.911] Latest Torizon IDE published :: 3.4.100

[04-30 11:06:39.911] Telemetry is enabled

[04-30 11:06:39.911] Extension collects completely anonymous telemetry data about templates usage. Participation in this anonymous program is optional, and you may opt-out if you’d not like to share any information. Check: Settings - Data Collection | Toradex Developer Center

[04-30 11:06:39.911] Telemetry allows us to accurately gauge templates usage. This data will help us to focus better on the most used templates, adding new features and putting effort in the right place.

[04-30 11:06:39.911] User defined host IP address found

[04-30 11:06:39.911] Host IP address OK

[04-30 11:06:39.912] Bash as default shell OK

[04-30 11:06:39.929] Docker installed OK

[04-30 11:06:40.06] Docker running OK

[04-30 11:06:40.126] Docker compose OK

[04-30 11:06:40.627] PowerShell OK

[04-30 11:06:40.671] git OK

[04-30 11:06:40.750] dig OK

[04-30 11:06:40.771] avahi-resolve OK

[04-30 11:06:40.848] nmap OK

[04-30 11:06:40.903] iputils-ping OK

[04-30 11:06:40.914] file OK

[04-30 11:06:40.925] sshpass OK

[04-30 11:06:41.018] iproute2 OK

[04-30 11:06:41.076] rsync OK

[04-30 11:06:41.101] python3 OK

[04-30 11:06:41.110] pipx OK

[04-30 11:06:41.111] Cloning project templates

[04-30 11:06:41.111] Templates repo: GitHub - torizon/vscode-torizon-templates: VS Code Torizon Integrated Development Environment Templates · GitHub

[04-30 11:06:41.111] Templates branch: bookworm-7

[04-30 11:06:41.111] Templates tag/hash: v3.3.0

[04-30 11:06:41.136] Project templates clone of branch bookworm-7 OK

[04-30 11:06:41.838] Project templates fetched OK

[04-30 11:06:41.872] Checkout templates repo to tag origin/bookworm-7 OK

[04-30 11:06:43.021] Error trying to setup xonsh

[04-30 11:06:43.021] ERROR :: Xonsh is not installed, Xonsh is required.

[04-30 11:06:43.021] WARNING :: Project name not found in workspace metadata for single container workspace, or it matches the workspace name.

[04-30 11:06:43.023] Checking connected devices …

[04-30 11:06:43.023] Scanning Torizon devices …

[04-30 11:06:43.032] Debian bookworm packages list load OK

[04-30 11:06:43.032] Configuring debug id_rsa …

[04-30 11:06:43.032] Debug id_rsa OK

[04-30 11:06:43.032] ERROR :: Errors during the initialization of Torizon IDE Extension.

[04-30 11:06:43.033] HOUSTON WE HAVE A PROBLEM!

[04-30 11:06:43.033] PLEASE READ THE LOGS!

[04-30 11:06:43.033] ERROR :: Please share this log on https://community.toradex.com

[04-30 11:06:43.140] Checking host ip sanity …

[04-30 11:06:50.381] Host ip is OK

[04-30 11:06:50.385] Device 10.40.100.5 set as Docker Host

4

Issue Identified

Based on your log, the error is clear: “ERROR :: Xonsh is not installed, Xonsh is required.” This is causing the initialization failure of the Torizon IDE Extension.

Ubuntu 24.04 Compatibility Issue

The main issue is that you’re running Ubuntu 24.04 in WSL. According to the official documentation, the Torizon IDE Extension currently supports Ubuntu 22.04 for WSL environments(1). Ubuntu 24.04 is not officially supported, which explains why the xonsh dependency installation is failing.

Recommended Solutions

1. Use Supported Ubuntu Version

Switch to Ubuntu 22.04 in WSL, which is the officially supported distribution(2)(1). You can install Ubuntu 22.04 from the Microsoft Store or using:

wsl --install -d Ubuntu-22.04

2. Use the Installation Wizard (Recommended)

Instead of manual setup, use the Torizon IDE Installation Wizard which automatically installs and configures the extension on Windows(2). This wizard handles all dependencies automatically and is the recommended approach.

3. Manual Xonsh Installation (If Continuing with Ubuntu 24.04)

If you must continue with Ubuntu 24.04 (unsupported), you can try manually installing xonsh:

sudo apt update
sudo apt install python3-pip
pip3 install xonsh

Then restart VS Code and try activating the extension again.

Important Notes

  • The Torizon IDE team does not support or test installations on Ubuntu 24.04(1)
  • Issues encountered on unsupported distributions may not have known solutions
  • For the best experience, use the Installation Wizard with the supported Ubuntu 22.04 distribution(2)

Next Steps

  1. Switch to Ubuntu 22.04 for official support
  2. Use the Installation Wizard for automated setup
  3. If issues persist on supported platforms, ensure VS Code is installed on Windows (not in WSL) and that you’re using Docker Engine (not Docker Desktop)(2)

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

5

@ToradexAI
xonsh IS installed. For some reason, it thinks it isn’t. Even the link is there.

6

This points to your password being set wrong or not entered. Could you confirm if the prompt to input the password is being shown?

7

@matheus.tx
Hi Matheus,
No, no request for PW. Also, the link is there despite what the log says. I did get another update of the VSC, maybe there is something going on there.
Also, for quite a while every time I load VSC and when it is running the extension, I get this message saying VSC needs to restart as “something” changed. If I reload it, it just repeats the case.
But now because of this not thinking xonsh is not installed, it doesn’t do the powershell connection. However, it seems to debug and work OK, despite all the hoopla.

Steve

Oh and when did 24.04 stop being supported? I went back through the links the AI mentioned above and couldn’t find any specific Ubuntu version listed at all. Maybe I just missed it…