Unable to Install Additional Templates and Workloads with Flatpak .NET SDK Extension

I'm using the Flatpak version of JetBrains Rider and have followed the recommendation to use the .NET SDK Extension provided by Flatpak. I installed the .NET 9 SDK Extension and set the environment variable FLATPAK_ENABLE_SDK_EXT=dotnet9 as described in the documentation.

When I launch Rider, the IDE successfully detects the .NET framework, and I'm able to create and run applications (console apps, web apps, etc.), which works as expected.

However, when I try to install additional templates or workloads (such as Maui or Aspire) through Rider's interface, nothing happens. There is an option in Rider to install these workloads, but when I click the install button, no progress occurs, and no templates are added.

Workaround: If I don't use the Flatpak-provided .NET SDK extension and instead install the .NET SDK manually (by selecting the "Install SDK" option within Rider), everything works fine, and I can install additional templates and workloads without issues.

Steps to Reproduce:

1. Install the .NET 9 SDK Extension via Flatpak.
2. Set the environment variable FLATPAK_ENABLE_SDK_EXT=dotnet9.
3. Launch JetBrains Rider via Flatpak.
4. Try to install additional templates or workloads (e.g., Maui or Aspire) via Rider's Tools → Install Workload.
5. Nothing happens.

Expected Behavior: I expect that the .NET SDK Extension provided by Flatpak would allow the installation of additional templates and workloads (like Maui and Aspire) directly within Rider.

Actual Behavior: The Maui and Aspire workloads do not install when using the Flatpak .NET SDK extension.

Environment:

>
> Operating System: Fedora 41
> JetBrains Rider: Flatpak version
> .NET SDK: .NET 9 SDK Extension via Flatpak

Additional Information: When I use the Rider-provided method to install the .NET SDK (via Rider’s interface), everything works fine, including the installation of additional workloads and templates.

Start at the Flatpak .NET SDK extension setup using FLATPAK_ENABLE_SDK_EXT=dotnet9, then reproduce the failure through Rider's Tools → Install Workload flow. Compare that behavior with Rider's manually installed SDK path; done means Maui or Aspire workloads and their templates install successfully. No repository file or test is named in the report.

Written by the indexing model from the issue text.