-
Notifications
You must be signed in to change notification settings - Fork 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
Plotting fails in Big Sur for some - both x86_64 and M1 [BUG] #1189
Comments
I installed Atom and it installed some of its prerequisites and now plotting works on Big Sur... |
strange the Atom prereqs amended the issue as the Atom Electron version doesn't seem to support m1 yet RE atom/atom#21688 |
Hrm - electron/electron#22996 |
on BigSur M1 (fresh with virtually nothing installed other than Chia) it works if I launch from the command line:
at least it starts, prints log and created temporary files, I did not complete a k32. When I launch it from Finder, the "create plot" button just brings me back to the plots tab with no new item in the list, nor a process running in the background, plotting. |
I also experienced a plotting issue on Mac OS Catalina 10.15.7, on a machine that was not M1. |
Still an issue with RC9 |
Painfully aware that this is still a problem . Plotting from Terminal works great in the interim. https://github.com/Chia-Network/chia-blockchain/wiki/Quick-Start-Guide#macos |
I believe this can be closed. it works in 1.0 |
Describe the bug
Plotting fails in Big Sur - both x86_64 and M1 for some but not everyone.
To Reproduce
Install on Big Sur. It may require not having dev tools installed to replicate though it will replicate on Big Sur on M1 with devtools installed.
On x86_64 plotting "starts" but if you open the plot log all you see is one entry "Loading...".
On Big Sur it doesn't even pop the creating plots page.
This came in in RC3 with the switch to Click and the RC4 fix didn't fix this.
debug.log from M1:
debug.log from x86_64
The text was updated successfully, but these errors were encountered: