Thank you for providing the platform details and the VS Code logs! The error message you found is very helpful:
EACCES: permission denied, mkdir '.conf'
This indicates a permissions issue where the Torizon IDE Extension cannot create the necessary .conf directory during activation.
Root Cause
The error occurs when the extension tries to create configuration files but lacks proper write permissions in the workspace or user directory. This is particularly common in WSL environments where file permissions can be complex between Windows and Linux filesystems.
Solutions to Try
1. Check Workspace Permissions
Ensure your VS Code workspace directory has proper write permissions:
# Navigate to your workspace directory
cd /path/to/your/workspace
# Check current permissions
ls -la
# Fix permissions if needed
chmod -R 755 .
2. WSL File System Location
Since you’re using WSL, make sure you’re working within the WSL filesystem (not Windows filesystem mounted in WSL):
- Recommended: Work in
/home/username/ or similar Linux paths
- Avoid: Working in
/mnt/c/ (Windows filesystem) where permission issues are common(1)
3. VS Code Installation Method
The documentation warns that the IDE Extension will not work with VS Code installed via Snap or Flatpak(2). Ensure you’re using the standard VS Code installation.
4. Extension Reinstallation
Try completely removing and reinstalling the extension:
- Uninstall the Torizon IDE Extension
- Close VS Code completely
- Restart WSL
- Reinstall the extension from the marketplace
5. Manual Directory Creation
As a workaround, you can try manually creating the .conf directory with proper permissions:
mkdir .conf
chmod 755 .conf
Additional Debugging
If the issue persists, check the internal VS Code logs again after trying these solutions(3). The Developer Tools Console may reveal additional permission-related errors or confirm if the issue is resolved.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
