The authentication library used by Storage Explorer has failed to start properly.

[mohammad-anbari-maersk]

Preflight Checklist

• I have installed the latest version of Storage Explorer.
• I have checked existing resources, including the troubleshooting guide and the release notes.
• I have searched for similar issues.

Storage Explorer Version

v1.25.1

Regression From

No response

Architecture

x64

Storage Explorer Build Number

No response

Platform

macOS

OS Version

12.6

Bug Description

I am using the mc book M1 pro
when I am opening the azure storage explore the error dialog pop up with the following error message:

"The authentication library used by Storage Explorer has failed to start properly. Please refer to the troubleshooting guide for help. Verbose authentication logging has been enabled.

Error:Hub Controller process exited prematurely with signal 'SIGABRT'."

Steps to Reproduce

1. Launch the azure storage explorer on Mac M1 pro

Actual Experience

When I am opening the azure storage explore the error dialog pop up with the following error message:

"The authentication library used by Storage Explorer has failed to start properly. Please refer to the troubleshooting guide for help. Verbose authentication logging has been enabled.

Error:Hub Controller process exited prematurely with signal 'SIGABRT'."

Expected Experience

No response

Additional Context

No response

[MRayermannMSFT]

@mohammad-anbari-maersk can you please reproduce the issue and then provide us with the authentication logs? Please see the troubleshooting guide for more info: https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-troubleshooting?tabs=Windows%2C2204#authentication-logs

[mohammad-anbari-maersk]

@MRayermannMSFT I have reproduced the issue and this is the log file:
logs.zip

[mohammad-anbari-maersk]

Hi @MRayermannMSFT
Is there any update ?

[mchalecki]

I also have this problem. Is there any follow-up?

[MRayermannMSFT]

Hey y'all, sorry, it took some digging to find something good for you to try.

I stumbled upon this GitHub issue for some other software: PowerShell/PSReadLine#1464

It makes it sound like a potential cause of the The system cannot open the device or file specified exception is the permissions of your /tmp and /private/tmp folders. Feel free to read through the issue yourself, but ultimately it'd be great if y'all could try running chmod 777 /private/tmp and chmod +t /private/tmp. There's a chance you'll need to run as sudo but I would try without first.

If that doesn't work, it could be that tmp is full in which you'll want to consider doing as this comment recommends: PowerShell/PSReadLine#1464 (comment)

[mohammad-anbari-maersk]

Hi @MRayermannMSFT

It's worked for me after running those chmod commands,
Thanks a lot for your help and time.

[MRayermannMSFT]

Glad to worked out. I will close this issue as mitigated. If anyone else has this issue and the existing info does not resolve it for you, then please open a new issue. Thanks.