Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[dotnet, golang] Connot access to extension SDK despite it being installed and FLATPAK_ENABLE_SDK_EXT being used

Open
  • Is something wrong?
#434 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, shell, vscode
Domain
devtools

Research direction

Start by reproducing the reported flatpak run com.visualstudio.code commands with FLATPAK_ENABLE_SDK_EXT=dotnet and golang, then inspect /usr/lib/sdk/ inside the container and compare the installed extension IDs. Done means identifying why dotnet7 and golang are unavailable while dotnet6 works, or documenting the supported extension configuration.

Written by the indexing model from the issue text.

Description

I installed VSCode through Flatpak, and followed the instruction in the first run text file, but VSCode as well as VScode-OSS both do not detect the Flatpak sdk extension.

I tried both FLATPAK_ENABLE_SDK_EXT=dotnet and FLATPAK_ENABLE_SDK_EXT=dotnet7 before flatpak run com.visualstudio.code, both returned Requested SDK extension "dotnet" is not installed

Installed SDKs:

$ flatpak list | grep -i sdk
Freedesktop SDK	org.freedesktop.Sdk	22.08.15	22.08	flathub	system
.NET Core SDK extension	org.freedesktop.Sdk.Extension.dotnet7	7.0.401	23.08	flathub	system
Go programming language Sdk extension	org.freedesktop.Sdk.Extension.golang	1.21.0	23.08	flathub	system

Same problem with the golang extenssion and FLATPAK_ENABLE_SDK_EXT=golang

In all cases /usr/lib/sdk/ is empty.

Edit: the command $ find / -iname dotnet returns no result when executed inside the container.

Edit2: Something noteworthy I ended up finding is that the dotnet6 sdk do work as intended, but both dotnet5, dotnet7 and golang don't.

Dominant language
Shell
Stars
217
Forks
81
Avg merge
4d 12h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flathub/com.visualstudio.code

All issues in flathub/com.visualstudio.code

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.