Package Details: storageexplorer 1.10.1-1

Git Clone URL: (read-only)
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: 12
Popularity: 1.271305
First Submitted: 2017-02-23 15:38
Last Updated: 2019-09-22 07:28

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

faultylee commented on 2018-08-17 02:37

Thank you for the info, I tried to follow the steps by slack and vscode, still getting segfault (but no core dump). Then I noticed glibc-2.28-4 is out 6 days ago, updated it, problem resolved. Let me know if you guys still getting segfault after updating

maetthu commented on 2018-08-16 13:00

The segfault is due to incompatibilities between latest glibc update and electron. Solution seems to be to bundle glibc, see and upstream bug

faultylee commented on 2018-08-16 12:51

@Lindhe I just realized I'm getting the same thing. Sorry for not testing it. I'll see what I can do about this.

Lindhe commented on 2018-08-16 12:48

I'm getting segfault when running it... Anyone else?

faultylee commented on 2018-06-25 04:07

@nhjm thanks for sharing. It's a good note for other users. FYI fs.inotify.max_user_instances settings is system dependent, it's required for many other packages depending on your setup, i.e. Atom, Dropbox...etc. I don't think it's a good idea to include in the install script.

nhjm449 commented on 2018-06-15 23:25

FYI: In order to get this app to work, I had to increase the number of allowed inotify instances.

sysctl -w fs.inotify.max_user_instances=1024

System.IO.FileSystemWatcher was throwing a "The configured user limit (128) on the number of inotify instances has been reached." exception upon startup, causing the app to display a "Please install .NET Core 2.0" dialog.

faultylee commented on 2018-05-19 23:11

@johnhamelink the checksum seems fine. If you're using AUR helpers, there might be a cached copy of StorageExplorer-linux-x64.tar.gz from the previous version, which caused the checksum to fail. I just tested that and it works after I deleted StorageExplorer-linux-x64.tar.gz. Can you confirm on your end? I'll try to see if there's away to avoid this, though most recommendation points to using makepkg as the standard method and understanding how it works behind the scene.

johnhamelink commented on 2018-05-16 08:36

storageexplorer is currently failing its validity check

faultylee commented on 2018-05-12 02:37

Noted @cinatic, I've updated to 1.1.0 at the same time

cinatic commented on 2018-05-03 13:41


storage explorer needs community/dotnet-runtime, you maybe want to add it as dependency