Package Details: storageexplorer 1.28.1-1

Git Clone URL: (read-only, click to copy)
Package Base: storageexplorer
Description: Microsoft Azure Storage Explorer is a standalone app from Microsoft that allows you to easily work with Azure Storage data on Windows, macOS and Linux.
Upstream URL:
Keywords: azure cloud microsoft storage
Licenses: unknown
Provides: storageexplorer
Submitter: XenGi
Maintainer: faultylee
Last Packager: faultylee
Votes: 26
Popularity: 0.064957
First Submitted: 2017-02-23 15:38 (UTC)
Last Updated: 2023-03-12 07:45 (UTC)

Pinned Comments

faultylee commented on 2022-08-05 14:48 (UTC)

The latest update is now using .NET Core 6.0, should help resolve some of the issues some of you had previously around installing .NET Core 3.1

Latest Comments

1 2 3 4 5 6 7 Next › Last »

faultylee commented on 2023-01-29 09:44 (UTC)

I've updated the deps to dotnet-runtime-6.0.

Apology for not noticing this earlier and for the delay in the updates. I was away on holiday.

@rlees85 @lukaszmoroz

rlees85 commented on 2023-01-10 21:53 (UTC) (edited on 2023-01-10 21:55 (UTC) by rlees85)

It makes no sense to depend on dotnet-runtime when installing this package does not work and it explicitly needs dotnet-runtime-6.0.

Could this be fixed?

Its annoying to have to manually make changes to the PKGBUILD every time it needs to be built.

edit: to say thanks for maintaining this

lukaszmoroz commented on 2022-12-08 08:09 (UTC)

Shouldn't then this package depend on a specific version, i.e. dotnet-runtime-6.0?

faultylee commented on 2022-08-05 14:48 (UTC)

The latest update is now using .NET Core 6.0, should help resolve some of the issues some of you had previously around installing .NET Core 3.1

lkrms commented on 2022-06-25 06:33 (UTC)

I lost of a bunch of time to the .NET Core 3.1 issue this week and was surprised there were no dotnet-*-3.1-bin packages in the AUR, so I've created one:

I haven't figured out why dotnet-runtime-3.1 disappeared from community--it's still supported by Microsoft and the package doesn't appear to have been removed from the community repo--so I've added -bin to the various dotnet- and aspnet- 3.1 package names in case official versions return. Unfortunately this means dotnet-runtime-3.1 might not resolve to dotnet-runtime-3.1-bin (I'm not sure if any AUR helpers use provides to resolve dependencies), but if you install it explicitly, storageexplorer should work. 🤞🏻

faultylee commented on 2022-06-23 02:58 (UTC)

@crimson, I found a workaround on the ICU version issue based on

I've updated the package with the added envvar. It disables globalization support. Let me know if anyone else faces issue with this change.

crimson commented on 2022-06-18 10:43 (UTC) (edited on 2022-06-18 19:58 (UTC) by crimson)

I was still getting Please ensure you have .NET Core 3.1 installed even though I had 3.1 sdk and runtime installed.

It turned out that latest icu 71.1-1 (International Components for Unicode library) was causing compatibility issues.

I solved it by installing icu70 70.1-1 from AUR


Found a workaround without installing any new packages, setting environment variable: CLR_ICU_VERSION_OVERRIDE=71.1

Note that you will need to change this variable every time ICU updates until this issue gets fixed

faultylee commented on 2022-05-30 15:22 (UTC) (edited on 2022-05-30 15:25 (UTC) by faultylee)

NOTE: If you are getting Please ensure you have .NET Core 3.1 installed

I found something that works.

Double check with dotnet --info to make sure you don't have 3.1.* installed. Download following

You need to chmod +x then execute it as follows to install version 3.1.25. I found out about the argument through trial and error following their official doc(

sudo ~/.dotnet/tools/ --install-dir /usr/share/dotnet -channel 3.1 -version 3.1.25 -Runtime dotnet

faultylee commented on 2022-05-30 15:06 (UTC)

@armadillo I just realized I actually have 3.1.20 installed, I'm not sure how, still figuring out.

$ dotnet --info

Host (useful for support):
  Version: 6.0.2
  Commit:  839cdfb0ec

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.NETCore.App 3.1.20 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.2 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

I looked into and tried using but the url for the runtime was wrong. No luck so far. I'm getting quite busy this week. I'll figure something out in the coming weekend.

armadillo commented on 2022-05-30 06:33 (UTC) (edited on 2022-05-30 06:49 (UTC) by armadillo)

@faultylee - thanks. I followed the steps you suggested but still get the error. The GUI loads, with an error dialog on top, the full text of which is

The authentication library used by Storage Explorer has failed to start properly. Please ensure you have .NET Core 3.1 installed. If .NET Core 3.1 is already installed then refer to the troubleshooting guide for help. Verbose authentication logging has been enabled.

Error:Hub Controller process exited prematurely with exit code 150.

If I click the OK button in this dialog the GUI then closes.

EDIT - the Storage Explorer logs folder includes entries such as

05/30/2022 07:37:13 : Error : Hub Controller process exited prematurely with exit code 150.

05/30/2022 07:37:13 : Information : HubController PID 38698 exited with code 150.

05/30/2022 07:37:13 : Information : Log configuration: $SERVICEHUBTRACELEVEL="ALL"

05/30/2022 07:37:13 : Information : Starting Service Hub controller '/opt/StorageExplorer/resources/app/ServiceHub/Controllers/microsoft-servicehub-controller/Microsoft.ServiceHub.Controller dbf258454b'.

05/30/2022 07:37:13 : Error : HubController PID 38700 stderr: It was not possible to find any compatible framework version

The framework 'Microsoft.NETCore.App', version '3.1.0' (x64) was not found.

  • The following frameworks were found:

    6.0.2 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.