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 not opening on windows [With solution] #3605

Open
FKrauss opened this issue Nov 13, 2019 · 3 comments
Open

Bisq not opening on windows [With solution] #3605

FKrauss opened this issue Nov 13, 2019 · 3 comments

Comments

@FKrauss
Copy link
Member

@FKrauss FKrauss commented Nov 13, 2019

Description

Bisq simply doesn't open on windows. You click the icon, nothing happens.

This is an issue to help others solve the problem as we had users who found how to fix it and we probably should use this as the starting point for a bug fix

Version

all (known the start on 1.7)

Steps to reproduce

Have Special chara

  1. Install bisq
  2. Have special characters in your username, and thus the bisq path on Windows, such as á (very common in Portuguese) or ø (Danish)
  3. try to open Bisq
  4. sit and stare and the empty screen. No error messages nothing happens

Expected behaviour

Bisq opens and you are able to use it

Actual behaviour

Nothing happens

Device or machine

Windows 7 and 10

Solution

Change the installation directory to NOT include any special characters anywhere in its path.

@ripcurlx

This comment has been minimized.

Copy link
Member

@ripcurlx ripcurlx commented Nov 14, 2019

@devinbileck Do you think there is anything we can configure in install anywhere or the Windows build configuration to fix this problem?

@devinbileck

This comment has been minimized.

Copy link
Member

@devinbileck devinbileck commented Nov 14, 2019

I will look into reproducing this and investigating a solution.

devinbileck added a commit to devinbileck/bisq that referenced this issue Nov 20, 2019
Prior to starting the installation, check if the install location
contains special characters and if so use a different default install
location as well as display a prompt to the user providing additional
details.

This is in response to bisq-network#3605, for which a proper solution has yet to be
found.
@devinbileck

This comment has been minimized.

Copy link
Member

@devinbileck devinbileck commented Nov 20, 2019

I am able to reproduce the issue, but have yet to find the cause. The exe exits shortly after launching it with a return code of 1 while attempting to read runtime\lib\modules. I have been unable to determine anymore than that. I am leaning towards this being an issue with javapackager. We can re-evaluate this issue once we move to a newer Java version with a newer javapackager tool.

For now, I have updated the installer in order to mitigate and workaround this issue in #3642.

ripcurlx added a commit that referenced this issue Nov 20, 2019
* Implement installation path check on Windows

Prior to starting the installation, check if the install location
contains special characters and if so use a different default install
location as well as display a prompt to the user providing additional
details.

This is in response to #3605, for which a proper solution has yet to be
found.

* Ensure the destination location dialog is always shown

This resolves #552

* Show the Welcome dialog

Rather then potentially being greeted with the newly implemented
prompt on the destination location dialog if they have special
characters in their install path, greet the user with the Welcome
dialog when they initially launch the installer.

* Reorder/group setup items logically
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.