-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac OS Catalina 10.15 seems to be PREVENTING access Documents and Desktop folders ... #2843
Comments
I had the same issue on macOS Catalina, I moved the file to my home folder and renamed the file to a shorter name. This did indeed do the trick for me. |
I had to run as "sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher" to get correct permissions to write to the SD card. Running the app normally didn't seem to work. |
same here, running as sudo did the trick, it gives you an additional dialog and asks if it's okay for Etcher to write to a removable disk. Didn't get this dialog when running as my user. |
I don't get any dialog, running with |
As long as you are logged into your Mac as an Admin user you will have access to sudo. As @semicolonsnet mentioned Open a terminal window and navigate all the way into the contents of the application and then open the app. Here is a copy of my output for reference. |
@jsajovic Yes, I know that. Executing |
@idoodler What directory is the image you want to flash in? |
@DG12 The image is in the |
@idoodler Try moving the image file to /tmp or /private/tmp . |
@DG12 No, same error message in the BalenaEtcher application. I executed the binary with sudo... |
This message: "The writer process ended unexpectedly" in not the " "something went wrong" message you said you received earlier. |
@DG12 Oh, I thought you ment this message because you its less to write. |
@idoodler could you please paste here the output of the devtools console? |
Moving the linux iso to my user folder and then running the app under sudo (sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher) did the trick. I did still get the new Catalina prompt asking to confirm access to the USB drive but no further issues. Thanks for the tips! |
sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher worked great for me. I also renamed my image file to a.img and left it in the Downloads folder. OSX 10.15 19A546d with Etcher 1.5.56 |
To repeat my request which will assist in isolating the specific problem: |
@DG12 We'll do, there are some new error messages we need to flesh out when the generic "EPERM" error appears, and in this case it's due to the changes to OSX Catalina. See #2833 (comment) for a workaround and let's use that as the issue for Catalina changes, closing this one |
Same here.... Running as sudo worked for me. |
Same with me. Working with balenaEtcher 1.5.58 on macOS Catalina 10.15. It worked only when run as sudo. |
running as sudo is working for me also thanks @semicolonsnet |
thanks, |
I tried with balenaEtcher version 1.5.30 with the command After updating the app to version 1.5.58, the app is working fine now! |
I had the same problem, and worked for me the sudo solution. Maybe something interesting is that with this method I had to allow access to the USB drive for terminal. |
Thank you @semicolonsnet! Worked beautifully for me. |
Great, thanks! |
Same, running That said. This feels a bit unsafe. |
@diver-down It's being fixed in #2939 |
sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher |
"sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher" worked! |
Thx !! |
I am on macOS 10.15.1 and I had to |
According to #2833 (comment) this should be fixed in the latest versions of Etcher. (making |
Catalina 10.15.2 this is not a problem |
Balena Etcher 1.5.69 on macOS 10.15.1 works with sudo. Thanks. |
I encountered this error on macOS Big Sur 11.3 I resolved it by ensuring System Preferences > Security & Privacy > Privacy > Files and Folders > Removal Volumes was enabled for balenaEtcher |
"Something went wrong"
Image in Documents directory fails!
Moving it elsewhere proceeds successfully.
PLEASE (at least) revise the error message when "operation not permitted, open " occurs to be more specific rather than mentioning corruption.
I have submitted a feedback issue to apple ( FB6392670).
++++++++
Sorry about the pervious various confusing updates here.
OMG! On a whim, I moved the image to a high level directory and renamed it to a short name and it works.
++++++++++++++++++++++++++++++++++++++++++++++
From devtools; console:
Validate on success: true
/Volumes/DATA/dgerman/.bin/balenaEtcher.app/Contents/Resources/app.asar/node_modules/raven-js/dist/raven.js:58
Error: EPERM: operation not permitted, open ‘/Volumes/DATA/dgerman/Documents/computerstuff/hardware/pi/SDimages/i/2019-06-20-raspbian-buster-lite.zip’
/Volumes/DATA/dgerman/.bin/balenaEtcher.app/Contents/Resources/app.asar/node_modules/raven-js/dist/raven.js:58
Sun Jun 30 2019 08:33:57 GMT-0400 (EDT) Open modal ({“name”:“warning”,“applicationSessionUuid”:“c8c7003a-5741-4484-b98c-4f37fe3cabb6”,“flashingWorkflowUuid”:“521ab4a8-f281-4360-8af3-6964b792d80a”,“sample”:0.1})
/Volumes/DATA/dgerman/.bin/balenaEtcher.app/Contents/Resources/app.asar/node_modules/raven-js/dist/raven.js:58
{“stack”:“Error: EPERM: operation not permitted, open ‘/Volumes/DATA/dgerman/Documents/computerstuff/hardware/pi/SDimages/i/2019-06-20-raspbian-buster-lite.zip’”,“message”:“EPERM: operation not permitted, open ‘/Volumes/DATA/dgerman/Documents/computerstuff/hardware/pi/SDimages/i/2019-06-20-raspbian-buster-lite.zip’”,“name”:“Error”,“code”:“EPERM”,“syscall”:“open”,“errno”:-1,“image”:“2019-06-20-raspbian-buster-lite.zip”}
console.(anonymous function) @ /Volumes/DATA/dgerman/.bin/balenaEtcher.app/Contents/Resources/app.asar/node_modules/raven-js/dist/raven.js:58
/Volumes/DATA/dgerman/.bin/balenaEtcher.app/Contents/Resources/app.asar/node_modules/raven-js/dist/raven.js:58
Flash results Object
/Volumes/DATA/dgerman/.bin/balenaEtcher.app/Contents/Resources/app.asar/node_modules/raven-js/dist/raven.js:58
Terminating IPC server
The text was updated successfully, but these errors were encountered: