-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
App remain in white screen on MacOS Big Sur 11.1 on M1 #5877
Comments
Thanks for opening your first issue here! |
@andoniabedul Did it work for you in older versions? Could you please provide us with your output if you run |
Hi @ripcurlx! Sorry but I didn't test older versions, this it's my first attempt to use Bisq. Sure, if I run
I will try with older versions to see if I have different results. I will update the comments if I have different results. Regards, it's a pleasure for me help on something :-) |
Ah - I just read that you are running on an M1 chip. I personally haven't tried to run an existing binary with that setup. |
Building and running from source is a problem on an M1, per #5835, but I have no problem running the binary dmg distribution on Big Sur 11.2.3. Looking at the stack trace, I too thought maybe a malformed locale ID is causing the problem, but the above looks sane enough. |
I tested with 1.7.4 and it has the same result: white screen. I was thinking that maybe the issue it was that I don't have setted the LC_ALL, but I setted and nothing changed. I'm thinking in change the locale of my machine to see if I have the same error. |
Same error, white screen but in MacOs Monterey, but Intel Core i9
|
Great! I'm confirm that this issue it doesn't happen anymore on Bisq 1.8.4 Thanks! |
Description
The app doesn't start and it doesn't gives you errors. Only white screen.
Version
Bisq version: 1.7.5
Steps to reproduce
Expected behaviour
Open the app correctly.
Actual behaviour
Remain in a white screen
Screenshots
Device or machine
Mac OS version: Big Sur 11.1
Type of chip running: M1
Additional info
Trying to see whats going on, I opened the app as administrator using the command line, and I found this stack trace from Java:
Launching without sudo gives the same error.
The text was updated successfully, but these errors were encountered: