Electrum won't open on MacOS Big Sur (macOS 11, OSX 10.16, does not start) #6461
Comments
|
Added some infos here stracktrace sent to developer... https://www.reddit.com/r/Electrum/comments/i6j3nr/macos_big_sur_wont_start/ |
|
Is there any work in progress with this issues? |
|
Also encountering this issue. Please let me know if I can be of assistance in providing any logs etc. |
|
I suspect this is most likely due to problems upstream, with PyInstaller, or maybe even Python itself. For the time being, consider running from source. |
|
I paste a log from the console, maybe it will help: long log |
Happy to report that building from source alleviates the issue. |
|
probably related: pyinstaller/pyinstaller#5107 EDIT: actually this is only about building on macOS 11 |
did not work for me. Did you only run |
|
@SimonHausdorf I think they meant "running" from source, instead of bulding/creating a binary. See the README, though the instructions there need to be adapted a bit for MacOS. |
sorry could you explain the process ? thanks!! |
git clone https://github.com/spesmilo/electrum.git |
|
log |
|
related biolab/orange3#4878 |
|
related https://tickets.metabrainz.org/browse/PICARD-1950
This is what the PyQt lead maintainer says:
|
SomberNight
changed the title
|
I gather macOS 11 got released today. Alas, we shall try to have a workaround. |
SomberNight
changed the title
|
We can try to build with PyQt 5.13.1 as Picard does. @cculianu assuming this affects Electron Cash too, I'm just curious if maybe you have looked into it (?) |
|
I've built a test release for ElectrumSV with PyQt5 pinned to 5.13.1 and had a Bug Sur user who already experienced the 5.15 lock ups try it and they reported it works fine. |
|
4.0.2 was the one that still did the onefile thing and unarchived itself into a temp dir right? I suspect macOS hates that now since it "looks" a lot like a rootkit. EDIT: Yeah I see reports that 4.0.4 doesn't work for people either. Jesus. 4.0.4 has the proper .app? @rt121212121 is electrumsv a .app with real files in it or is it sort of a glorified "onefile"? Anyway I'll try it. @SomberNight: No, I haven't looked into it but I'll install Big Sur in a VM and check it out and let you know. Rant: Jesus Christ every darned release Apple breaks something or makes developer life hell. They keep locking down their platform with more restrictions. They are trying to turn (what was) a perfectly decent desktop OS into a glorified iPad. :( I''l look into it. Thanks for the heads-up. |
|
"Big Sur" .. more like "Bugs, Sir!", amirite? "Big Sur"prise -- your stuff stopped working. |
|
I don't know exactly what PyInstaller does on MacOS to make it work, but it is the dmg file that is produced. You should be familiar with it, since it's what Electron Cash and Electrum were doing when we forked. MacOS treats it as second class because it is not signed, but otherwise beyond the Big Sur issue, it seems like it works based on very limited testing. I expect the earlier version of PyQt5 will be sufficient to give Big Sur users a working build. It's hard to get away from PyInstaller given how much it reduces the build sizes. |
SomberNight
added a commit
to SomberNight/electrum
that referenced
this issue
Nov 14, 2020
This is the time of the year Apple breaks our mac builds, as usual. mac now has its own "binaries" requirements. This allows us to use an older version of PyQt5 in the mac binaries. For some reason if we bundle newer PyQt5, the built app will not start on macOS 11 (but will on older macOS). related: spesmilo#6461 in particular, see spesmilo#6461 (comment)
|
Option B here fixed the issue for me: |
|
I've reproduced the hang on a VM. Indeed bundling older PyQt, namely 5.13.1, fixes it. I'll close this issue as we have a workaround, however the root cause is still unknown. @sod1684 what command did you run exactly? |
This was referenced Nov 14, 2020
Closed
|
so when is the next release? |
|
What's the workaround? |
|
we have released Electrum 4.0.5 now, with the workaround of using old PyQt5 |
|
FYI -- a workaround that seems to work also is to set the env var: See: https://bugreports.qt.io/browse/QTBUG-87014 |
cculianu
added a commit
to Electron-Cash/Electron-Cash
that referenced
this issue
Jan 7, 2021
It turns out if we set the env var QT_MAC_WANTS_LAYER=1, then Qt>=5.13.2 will work correctly on macOS Big Sur. See: https://bugreports.qt.io/browse/QTBUG-87014 Related: spesmilo#6461
|
@cculianu Oh nice. One of the comments on stackoverflow also says
we should instead consider bumping to that then |
SomberNight
added a commit
to SomberNight/electrum
that referenced
this issue
Jan 7, 2021
|
Oh nice. Note I was unable to reproduce this issue at all in a Big Sur VM with PyQt 5.14.2 or 5.15.1 -- I presume it may only happen sometimes depending on graphics driver or something (I'm using VMWare Fusion). Do let me know if you can if that works! |
|
@cculianu I confirm that 5.15.2 seems to be working on my Big Sur VM (virtualbox) |
SomberNight
added a commit
to SomberNight/electrum
that referenced
this issue
Jan 7, 2021
|
Thanks @SomberNight -- I still couldn't reproduce it but knowing it works regardless on 5.15.2 is good to know, thanks for the follow-up. |
PiRK
added a commit
to Bitcoin-ABC/ElectrumABC
that referenced
this issue
Jan 11, 2021
This fixes a problem with a recent version of MacOS. See spesmilo#6461 (comment) If someone insists on making ElectrumABC run with a lower version of PyQt5, the alternative solution would be to use the same workaround as Electron-Cash Electron-Cash@1492b1d
EchterAgo
pushed a commit
to EchterAgo/Electron-Cash
that referenced
this issue
Mar 11, 2021
It turns out if we set the env var QT_MAC_WANTS_LAYER=1, then Qt>=5.13.2 will work correctly on macOS Big Sur. See: https://bugreports.qt.io/browse/QTBUG-87014 Related: spesmilo#6461
EchterAgo
pushed a commit
to EchterAgo/Electron-Cash
that referenced
this issue
Mar 11, 2021
It turns out if we set the env var QT_MAC_WANTS_LAYER=1, then Qt>=5.13.2 will work correctly on macOS Big Sur. See: https://bugreports.qt.io/browse/QTBUG-87014 Related: spesmilo#6461
EchterAgo
pushed a commit
to EchterAgo/Electron-Cash
that referenced
this issue
Mar 11, 2021
It turns out if we set the env var QT_MAC_WANTS_LAYER=1, then Qt>=5.13.2 will work correctly on macOS Big Sur. See: https://bugreports.qt.io/browse/QTBUG-87014 Related: spesmilo#6461
JeremyRand
pushed a commit
to namecoin/electrum-nmc
that referenced
this issue
May 7, 2021
This is the time of the year Apple breaks our mac builds, as usual. mac now has its own "binaries" requirements. This allows us to use an older version of PyQt5 in the mac binaries. For some reason if we bundle newer PyQt5, the built app will not start on macOS 11 (but will on older macOS). related: spesmilo#6461 in particular, see spesmilo#6461 (comment)
JeremyRand
pushed a commit
to namecoin/electrum-nmc
that referenced
this issue
May 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tried running Electrum 4.0.2 on MacOS Big Sur Beta 3 today.
If you start it, it's in the dock but no window opens. Right-click on the dock icon reveals "Application not responding". It's also permanently at 100% CPU in Activity Monitor. But even after an hour of waiting nothing happens.
The text was updated successfully, but these errors were encountered: