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

[Windows 10]Profile Name Error and White Screen Issue After Seedvault/Seed Use #992

Closed
Grachas opened this issue Apr 21, 2021 · 4 comments
Closed
Labels
bug report Something isn't working as intended

Comments

@Grachas
Copy link

Grachas commented Apr 21, 2021

Issue description

At first when you enter a profile name you get an error then if you click continue with the same name you can proceed. After attempting to use the seedvault created from Trinity or 81 character long seed, we get an empty unresponsive whitescreen.

Edit: Profile name issue might be due to the directory Firefly installed includes user name having "ğ" letter.

Wallet version

Desktop 1.0.0

System specification

Windows 10

Is it a repeatable issue?

Y

Steps To reproduce the issue

Explain how the maintainer can reproduce the issue.

  1. Enter your seed or use seedvault.
  2. Press continue.
  3. See whitescreen.

Expected behaviour

We expected to see the amount to be migrated.

Actual behaviour

Whitescreen occurs.

Errors

Screen1
Screen2

@Grachas Grachas added the bug report Something isn't working as intended label Apr 21, 2021
@Tombaaa
Copy link

Tombaaa commented Apr 22, 2021

This happend to me too, I use a user name with a special character 'ä', the user directory where the files are located contain this special character too.

See user path from Diagnostic:
User Path: C:\Users\Bänni\AppData\Roaming\Firefly

@Grachas
Copy link
Author

Grachas commented Apr 22, 2021

To be honest I'd rather not go through the hoops of changing the username folder in Windows 10. And it appears many people are encountering this issue so far, any news from the IF side?

@rajivshah3
Copy link
Member

@Grachas we're working on a patch for the issue

@rajivshah3
Copy link
Member

Closing as duplicate of #1015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Something isn't working as intended
Projects
None yet
Development

No branches or pull requests

3 participants