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

Support for unicode in the AppData path #265

Open
paalg opened this issue Feb 4, 2023 · 7 comments
Open

Support for unicode in the AppData path #265

paalg opened this issue Feb 4, 2023 · 7 comments

Comments

@paalg
Copy link

paalg commented Feb 4, 2023

To report critical security issues, DM the Core or Developer Teams instead of creating Github issues.

Describe the issue

I've had multiple errors lately, then I upgraded to version 1.3.17.01-c136d2b, and the application fails to start. I realized the application now does not support unicode in the path to the AppData\Roaming. Now I have a new folder under C:\Users\ with my name with � symbols where there should be å and æ:

C:\Users\P�l S�ter\AppData\Roaming\RaptoreumCore
insted of
C:\Users\Pål Sæter\AppData\Roaming\RaptoreumCore

What version of Raptoreum Core are you using?

1.3.17.01-c136d2b (upgraded from v1.2 something)

Machine specs:

  • OS: Windows 10 64 bit
@Bigpiggy01
Copy link
Collaborator

Hi there,
I am not able to reproduce that. Do you have any odd language packs installed? And was it installed with escalated priviliges?

@paalg
Copy link
Author

paalg commented Feb 5, 2023

I am not aware I have any odd language packs installed, I have a normal Windows 10 installed with Norwegian language. But the Raptoreum Core app is english. I don't remember if I used selected high privileges when installing.

I got problems synchronizing blocks, and ended up upgrading from version 1.2 to 1.3.17.01-c136d2b. It might be the function rebuilding block database that is the problem.

I get this error when I open the app now: "Error opening black database. Do you want to rebuild the block database now? [OK] [Abort]"
If i click OK, I get a new error "Error opening block database [OK]", and clicking OK just closes the app. If I instead choose Abort, then the app just closes.

If the files created now gives any help, I attached the list of files from command
C:\Users\P�l S�ter\AppData\Roaming\RaptoreumCore>dir /A /S
files.txt

@Blueskys379
Copy link

You will want to apply the bootstrap. Download one of the versions of the 1.3.17.00-01 bootstrap without the index and follow these steps.

How to bootstrap

On https://bootstrap.raptoreum.com/
Download the version of the bootstrap that matches your current wallet version.
Use bootstrap version that matches your wallet version

  • Stop wallet or daemon
  • In your wallets data directory delete folders:
    -- blocks
    -- chainstate
    -- evodb
    -- llmq
    and the powcache.dat file
  • Unpack bootstrap and copy the four folders and powcache.dat into your data directory
  • Start wallet
    Data Directory Locations:
  • Unix/Linux: $HOME/.raptoreumcore
  • Windows: %AppData%/raptoreumcore

@paalg
Copy link
Author

paalg commented Feb 11, 2023

  • I uninstalled Raptoreum Core
  • Removed all the files for Raptoreum under AppData (both from C:\Users\P�l S�ter\AppData\Roaming\RaptoreumCore and C:\Users\Pål Sæter\AppData\Roaming\RaptoreumCore)
  • Reinstalled v1.3.17.01-c136d2b making sure it was running with admin privileges
  • Started the application with admin privileges

From this clean install it still recreates the RaptoreumCore folder in both places, so parts of that version cannot handle the special characters in the users path.

The folders created where it cannot handle special characters might indicate where the problem lies:
image

@Bigpiggy01
Copy link
Collaborator

Looks like your default system language set to other than English, that shouldn't matter though as it works just fine on Danish with æøå in there.

The only circumstance I can break this under is having system set to Danish but running Mandarin during installation but that nukes unicode through out and has been an MS issue since Win 3.0 afaik.

@Bigpiggy01
Copy link
Collaborator

Interesting, I can reproduce this on the latest release with the installer.exe still not with the stand alone binaries.

@paalg
Copy link
Author

paalg commented Feb 27, 2023

Interesting, I can reproduce this on the latest release with the installer.exe still not with the stand alone binaries.

Yes, I can confirm I used the executable installer myself

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

No branches or pull requests

3 participants