Skip to content
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

Bisq v1.2.6 fails to start on macOS Mojave #3969

Closed
cbeams opened this issue Feb 13, 2020 · 2 comments
Closed

Bisq v1.2.6 fails to start on macOS Mojave #3969

cbeams opened this issue Feb 13, 2020 · 2 comments
Assignees

Comments

@cbeams
Copy link
Member

@cbeams cbeams commented Feb 13, 2020

Description

Version

v1.2.6

Steps to reproduce

Run the release build macOS executable on macOS Mojave (10.14.6 in my case)

Expected behaviour

App should start up as per usual without errors.

Actual behaviour

App freezes up at what appears to be the point the password prompt would show up. It behaves as if a modal popup (such as the password prompt) were present, but no such popup is visible. The UI becomes unresponsive to any click and system error bells are sounded on every attempt.

Screenshots

image

Notice the fuzzed-out background, again, as if a modal popup or dialog were in the foreground.

Device or machine

macOS 10.14.6 (18G103)

Additional info

We've verified that the change that caused this problem is PR #3883. It is unknown as to why exactly this change causes this problem, and why it causes it only on Mojave (Catalina is fine, and High Sierra is fine). @ripcurlx is preparing a v1.2.7 hotfix with this change reverted as we speak.

Note that at least two other users reported this issue as well:

  1. https://bisq.community/t/new-install-not-starting-up/8963/5
  2. https://www.reddit.com/r/bisq/comments/f3afym/stuck_on_latese_update_grey_screen/
ripcurlx added a commit that referenced this issue Feb 13, 2020
Fixes issue #3969

This setting prevented the startup of the app on macOS Mojave.
Possibly on some other older macOS versions as well.
@cbeams

This comment has been minimized.

Copy link
Member Author

@cbeams cbeams commented Feb 13, 2020

I can confirm that the newly-released v1.2.7 resolves this problem for me. Thanks @ripcurlx, and please close this issue at will.

@ripcurlx

This comment has been minimized.

Copy link
Member

@ripcurlx ripcurlx commented Feb 14, 2020

Closing as complete with v1.2.7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.