After updating Fedora 33 to 34 and dotnet 5.0.5 to 5.0.6 I get error regarding libhostfxr.so
See original GitHub issueWhen running dotnet ef migrations add MigrationName
I get:
A fatal error occurred. The required library libhostfxr.so could not be found.
If this is a self-contained application, that library should exist in [/home/alireza/.dotnet/tools/.store/dotnet-ef/5.0.6/dotnet-ef/5.0.6/tools/netcoreapp3.1/any/].
If this is a framework-dependent application, install the runtime in the global location [/usr/share/dotnet] or use the DOTNET_ROOT environment variable to specify the runtime location or register the runtime location in [/etc/dotnet/install_location].
The .NET runtime can be found at:
- https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=fedora.34-x64&apphost_version=5.0.6
Unfortunately, I don’t know if the error occurred after updating Fedora to 34 or only after upgrading dotnet to 5.0.6.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Troubleshoot .NET package mix ups on Linux
SDK #17570: After updating Fedora 33 to 34 and dotnet 5.0.5 to 5.0.6 I get error regarding libhostfxr.so: Fatal error: folder /host/fxr ...
Read more >.net - The required library libhostfxr.so could not be found. ...
Solved by adding this in whatever part of shell profile (it can be at the end): # Netcore export PATH=$PATH:$HOME/.dotnet/tools export ...
Read more >Errors with upgrade fedora 33 to 34
No packages marked for removal. Package fedora-release-common-33-4.noarch is already installed. Dependencies resolved. Nothing to do. Complete.
Read more >Fedora 34 upgrade from Fedora 33 blocked by rdma-core
Downgrading from it still does NOT allow upgrade to F34. So then I searched and found this bug, but it says the issue...
Read more >7124b168cc7e0c6a11120728ad...
Fatal error: libhostfxr.so couldn't be found. SDK #17570: After updating Fedora 33 to 34 and dotnet 5.0.5 to 5.0.6 I get error regarding...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That sounds right to me.
Unfortunately though, I believe the
dotnet-runtime-deps-5.0
problem is just another issue layered on top of the feed mixing. So, making an updated deps package makes progress, but doesn’t go all the way.IMO docs need to catch up and show how to properly use the Microsoft feed without the conflicts. (And how to uninstall the Microsoft feed to simply use the distro packages, which is generally preferable.)
This kind of thing can be an issue (although AFAIK not for Teams or Skype in particular). It looks like the Fedora 34 packages.microsoft.com repo doesn’t have anything other than .NET at the moment, but for example, the CentOS 8 https://packages.microsoft.com/centos/8/prod/ repo has PowerShell Core, MSSQL, some AAD packages, and other things I don’t recognize. Uninstalling the repo would break auto-updates for those.
The doc @omajid is working on at https://github.com/dotnet/docs/pull/24206 has instructions on how to keep the repo installed and just filter out just the .NET packages, to make this situation work. 🎉