-
Notifications
You must be signed in to change notification settings - Fork 783
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
Couldn't open wallet: invalid password. #4408
Comments
It's not an inquiry rather than comment on apparent new poor (but increasingly common) computer programming practice. |
This sounds like a bug, we do not "analyze" the entry before pressing enter and it should not say "invalid" beforehand. |
Good. Is there a way I should get a log? |
Which operating system are you using? How did you install monero-gui? Are you using a hardware wallet? |
Slackware 15 GNU/Linux (current 64-bit n86) always from official monero-gui GitHub's stable tag which currently points to monero-gui-linux-x64-v0.18.3.4.tar.bz2. I decompress it into a directory/folder and run (the following way with my wrapper script). I have no hardware wallet. First time monero-gui maybe installed in KDE & XFCE 'other' menu (which that XFCE menu disappeared or I'd use that entry sometimes).
|
Can you try to start monero-wallet-gui from the command line and say how often it says
in the logs? Does it match with the amount of characters your password has? |
Every time it says "Couldn't open wallet: invalid password" I enter my password, and it's valid. When such fields say something (password, personal/contact information, username, etc.) is 'invalid' before even started/finished entering, it's possibly nasty; alarms/confuses some/lesser users: best wait until entered it and only give any error message afterwards. Apparently there's a trend (all over World Wide Web) to analyse text boxes before anything is started/finished entering, and only disappear to tell user when they get it right, which is a bad (and lazy) practice, rather than not saying anything unless they get it wrong.
The text was updated successfully, but these errors were encountered: