[XMR] Monero - A secure, private, untraceable cryptocurrency - page 117.

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: BldSwtTrs on January 06, 2019, 04:55:36 PM

Quote from: dEBRUYNE on January 05, 2019, 02:39:28 PM

Quote from: ?? on ??

Quote from: dEBRUYNE on January 05, 2019, 01:28:25 PM

Quote from: BldSwtTrs on January 05, 2019, 01:17:53 PM

Quote from: dEBRUYNE on January 04, 2019, 11:48:52 AM

Quote from: BldSwtTrs on January 03, 2019, 07:02:28 PM

I have a problem with the GUI used with Ledger Nano S.
I have XMR in two different Ledger Nano S, I have created two different wallet file (the .keys file).
My daemon is synchronized. When I open the GUI with one Ledger and its associated .keys file, everything is OK.
But when I open the GUI with the second Ledger and its associated .keys file, there is a problem.

First, under "Network Status" it is written Synchronizing.
The lower progess bar indicates Daemon is synchronized.
The higher progress indicates Wallet blocks remaining 1740270 and it scans for all the blocks.

It lasts several hours and then, when the scanning of the whole blockchain is finished, it starts again...
This time under "Network Status" it is written Connected. But the scanning for the 1.7M blocks starts again and my balance is not showing, only "waiting for blocks". So basically this is a endless process and I cannot access my fund.

Did you set a restore height for the second Ledger Monero wallet? If not, please generate a new set of Ledger Monero wallet files for the second Ledger device with a proper restore height. You can use this guide for assistance:

https://monero.stackexchange.com/questions/9901/how-do-i-generate-a-ledger-monero-wallet-with-the-gui-monero-wallet-gui

OK now I haved setted a restore height and it solves this problem. But now I have a new problem with the GUI password.

With the first Ledger Nano S, the GUI password works fine and I can log in. But with the second Ledger, I cannot open the GUI, instead I have the error message: Couldn't open wallet: invalid password

I am sure I enter the exact same password than with my first Ledger. So why the GUI password is working with one device and not the other?

Which version of the GUI are you using? You can check on the Settings page of the GUI.

It's v0.13.0.4 (Qt 5.7.0)

Edit:
I didn't have this problem before I set restore height at 1,720,000.
And fwiw I set restore height only on the file associated with my second device, I didn't set any restore height on the file associated with my first device.

That's the right version. Can you perhaps generate a new set of Legder Monero wallet files (for the second device) and see if the issue persists?

I have generated new Ledger Monero wallet files and the issue persists each time: Couldn't open wallet: invalid password

Could you perhaps try a different password? Also, does your password contain any special (i.e. non-ASCII) characters?

BldSwtTrs

legendary

Activity: 861

Merit: 1010

Quote from: dEBRUYNE on January 05, 2019, 02:39:28 PM

Quote from: ?? on ??

Quote from: dEBRUYNE on January 05, 2019, 01:28:25 PM

Quote from: BldSwtTrs on January 05, 2019, 01:17:53 PM

Quote from: dEBRUYNE on January 04, 2019, 11:48:52 AM

Quote from: BldSwtTrs on January 03, 2019, 07:02:28 PM

I have a problem with the GUI used with Ledger Nano S.
I have XMR in two different Ledger Nano S, I have created two different wallet file (the .keys file).
My daemon is synchronized. When I open the GUI with one Ledger and its associated .keys file, everything is OK.
But when I open the GUI with the second Ledger and its associated .keys file, there is a problem.

First, under "Network Status" it is written Synchronizing.
The lower progess bar indicates Daemon is synchronized.
The higher progress indicates Wallet blocks remaining 1740270 and it scans for all the blocks.

It lasts several hours and then, when the scanning of the whole blockchain is finished, it starts again...
This time under "Network Status" it is written Connected. But the scanning for the 1.7M blocks starts again and my balance is not showing, only "waiting for blocks". So basically this is a endless process and I cannot access my fund.

Did you set a restore height for the second Ledger Monero wallet? If not, please generate a new set of Ledger Monero wallet files for the second Ledger device with a proper restore height. You can use this guide for assistance:

https://monero.stackexchange.com/questions/9901/how-do-i-generate-a-ledger-monero-wallet-with-the-gui-monero-wallet-gui

OK now I haved setted a restore height and it solves this problem. But now I have a new problem with the GUI password.

With the first Ledger Nano S, the GUI password works fine and I can log in. But with the second Ledger, I cannot open the GUI, instead I have the error message: Couldn't open wallet: invalid password

I am sure I enter the exact same password than with my first Ledger. So why the GUI password is working with one device and not the other?

Which version of the GUI are you using? You can check on the Settings page of the GUI.

It's v0.13.0.4 (Qt 5.7.0)

Edit:
I didn't have this problem before I set restore height at 1,720,000.
And fwiw I set restore height only on the file associated with my second device, I didn't set any restore height on the file associated with my first device.

That's the right version. Can you perhaps generate a new set of Legder Monero wallet files (for the second device) and see if the issue persists?

I have generated new Ledger Monero wallet files and the issue persists each time: Couldn't open wallet: invalid password

apuestasbitcoinnet

member

Activity: 150

Merit: 10

Bitcoiner

Monero Casinos.com

All the moneo casinos , some exclusive offers. Wink

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: ?? on ??

Quote from: dEBRUYNE on January 05, 2019, 01:28:25 PM

Quote from: BldSwtTrs on January 05, 2019, 01:17:53 PM

Quote from: dEBRUYNE on January 04, 2019, 11:48:52 AM

Quote from: BldSwtTrs on January 03, 2019, 07:02:28 PM

I have a problem with the GUI used with Ledger Nano S.
I have XMR in two different Ledger Nano S, I have created two different wallet file (the .keys file).
My daemon is synchronized. When I open the GUI with one Ledger and its associated .keys file, everything is OK.
But when I open the GUI with the second Ledger and its associated .keys file, there is a problem.

First, under "Network Status" it is written Synchronizing.
The lower progess bar indicates Daemon is synchronized.
The higher progress indicates Wallet blocks remaining 1740270 and it scans for all the blocks.

It lasts several hours and then, when the scanning of the whole blockchain is finished, it starts again...
This time under "Network Status" it is written Connected. But the scanning for the 1.7M blocks starts again and my balance is not showing, only "waiting for blocks". So basically this is a endless process and I cannot access my fund.

Did you set a restore height for the second Ledger Monero wallet? If not, please generate a new set of Ledger Monero wallet files for the second Ledger device with a proper restore height. You can use this guide for assistance:

https://monero.stackexchange.com/questions/9901/how-do-i-generate-a-ledger-monero-wallet-with-the-gui-monero-wallet-gui

OK now I haved setted a restore height and it solves this problem. But now I have a new problem with the GUI password.

With the first Ledger Nano S, the GUI password works fine and I can log in. But with the second Ledger, I cannot open the GUI, instead I have the error message: Couldn't open wallet: invalid password

I am sure I enter the exact same password than with my first Ledger. So why the GUI password is working with one device and not the other?

Which version of the GUI are you using? You can check on the Settings page of the GUI.

It's v0.13.0.4 (Qt 5.7.0)

Edit:
I didn't have this problem before I set restore height at 1,720,000.
And fwiw I set restore height only on the file associated with my second device, I didn't set any restore height on the file associated with my first device.

That's the right version. Can you perhaps generate a new set of Legder Monero wallet files (for the second device) and see if the issue persists?

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: ballayballay on January 05, 2019, 05:20:02 AM

Quote from: dEBRUYNE on December 29, 2018, 07:15:39 AM

Quote from: ballayballay on December 25, 2018, 03:12:03 AM

When I invoke monero-wallet-cli to order a transfer is there a way to avoid pass the password to it without using a "--password" command-line argument?

[1] You mean some kind of config file for monero-wallet-cli right? If so, you can create a config file and add the --config-file path/to/config/file flag upon launching monero-wallet-cli.

Thank you!

As for my second question I'm not sure of its very nature, it may be a bug report, or me neglecting something, or ...

Here it is, more clearly stated:
I use the cli wallet on Linux in a shellscript to directly make a transfer.

For example this script can invoke "./monero-wallet-cli --password=X --wallet-file=AFILENAME transfer important 11 SOMEADRESS SOME AMOUNT."

It nearly always works, but sometimes the cli wallet isn't able to make the requested transfer. The error message is then, for example, "Error: Not enough money in unlocked balance" or "Error: daemon is busy. Please try again later."

I understand the reasons, and I would like to let my shell script detect this "error". In order to do so it checks the exit code, in the "$?" pseudo-variable.

My problem is that 0 this pseudo-variable always contains 0, which means "no error".

Is it possible for the cli wallet program to exit with an adequate exit code? Ideally there would be a distinct code for each major type of error.

Thanks for the clarification. You basically want monero-wallet-cli to exit(1) after you incur an error right? I am not entirely sure whether that is possible currently.

Perhaps an idea to post your question on the Monero SE? Where other people may have some clever suggestion how to work around this particular issue.

https://monero.stackexchange.com/

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: ballayballay on January 04, 2019, 10:42:55 PM

Quote from: dEBRUYNE on December 29, 2018, 07:12:21 AM

Do you have any suggestions for improvements then (with respect to displaying the wallet name of the currently loaded wallet)?

To facilitate bean-counting I manage 2 wallets. As the GUI doesn't always show the name of the currently loaded wallet, before any operation I have to navigate around in order to know which wallet is loaded.

My suggestion is to have the GUI display the wallet name in the upper-right zone, where it now displays a line containing the Monero logo then "Monero", and on the next line the "Balance" label. Instead of "Balance" it may display "Balance in X" where X would be the wallet name (or as much characters of the beginning of the wallet filename that can be displayed there, given the current window-size restrictions).

Thank you!

Thanks for your suggestion. I have posted it in the GUI channel. Note that you can also open a new issue on the Monero GUI Github repository with your suggestion:

https://github.com/monero-project/monero-gui/issues/new

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: BldSwtTrs on January 05, 2019, 01:17:53 PM

Quote from: dEBRUYNE on January 04, 2019, 11:48:52 AM

Quote from: BldSwtTrs on January 03, 2019, 07:02:28 PM

I have a problem with the GUI used with Ledger Nano S.
I have XMR in two different Ledger Nano S, I have created two different wallet file (the .keys file).
My daemon is synchronized. When I open the GUI with one Ledger and its associated .keys file, everything is OK.
But when I open the GUI with the second Ledger and its associated .keys file, there is a problem.

First, under "Network Status" it is written Synchronizing.
The lower progess bar indicates Daemon is synchronized.
The higher progress indicates Wallet blocks remaining 1740270 and it scans for all the blocks.

It lasts several hours and then, when the scanning of the whole blockchain is finished, it starts again...
This time under "Network Status" it is written Connected. But the scanning for the 1.7M blocks starts again and my balance is not showing, only "waiting for blocks". So basically this is a endless process and I cannot access my fund.

Did you set a restore height for the second Ledger Monero wallet? If not, please generate a new set of Ledger Monero wallet files for the second Ledger device with a proper restore height. You can use this guide for assistance:

https://monero.stackexchange.com/questions/9901/how-do-i-generate-a-ledger-monero-wallet-with-the-gui-monero-wallet-gui

OK now I haved setted a restore height and it solves this problem. But now I have a new problem with the GUI password.

With the first Ledger Nano S, the GUI password works fine and I can log in. But with the second Ledger, I cannot open the GUI, instead I have the error message: Couldn't open wallet: invalid password

I am sure I enter the exact same password than with my first Ledger. So why the GUI password is working with one device and not the other?

Which version of the GUI are you using? You can check on the Settings page of the GUI.

BldSwtTrs

legendary

Activity: 861

Merit: 1010

Quote from: dEBRUYNE on January 04, 2019, 11:48:52 AM

Quote from: BldSwtTrs on January 03, 2019, 07:02:28 PM

I have a problem with the GUI used with Ledger Nano S.
I have XMR in two different Ledger Nano S, I have created two different wallet file (the .keys file).
My daemon is synchronized. When I open the GUI with one Ledger and its associated .keys file, everything is OK.
But when I open the GUI with the second Ledger and its associated .keys file, there is a problem.

First, under "Network Status" it is written Synchronizing.
The lower progess bar indicates Daemon is synchronized.
The higher progress indicates Wallet blocks remaining 1740270 and it scans for all the blocks.

It lasts several hours and then, when the scanning of the whole blockchain is finished, it starts again...
This time under "Network Status" it is written Connected. But the scanning for the 1.7M blocks starts again and my balance is not showing, only "waiting for blocks". So basically this is a endless process and I cannot access my fund.

Did you set a restore height for the second Ledger Monero wallet? If not, please generate a new set of Ledger Monero wallet files for the second Ledger device with a proper restore height. You can use this guide for assistance:

https://monero.stackexchange.com/questions/9901/how-do-i-generate-a-ledger-monero-wallet-with-the-gui-monero-wallet-gui

OK now I haved setted a restore height and it solves this problem. But now I have a new problem with the GUI password.

With the first Ledger Nano S, the GUI password works fine and I can log in. But with the second Ledger, I cannot open the GUI, instead I have the error message: Couldn't open wallet: invalid password

I am sure I enter the exact same password than with my first Ledger. So why the GUI password is working with one device and not the other?

ballayballay

newbie

Activity: 9

Merit: 9

Quote from: dEBRUYNE on December 29, 2018, 07:15:39 AM

Quote from: ballayballay on December 25, 2018, 03:12:03 AM

When I invoke monero-wallet-cli to order a transfer is there a way to avoid pass the password to it without using a "--password" command-line argument?

[1] You mean some kind of config file for monero-wallet-cli right? If so, you can create a config file and add the --config-file path/to/config/file flag upon launching monero-wallet-cli.

Thank you!

As for my second question I'm not sure of its very nature, it may be a bug report, or me neglecting something, or ...

Here it is, more clearly stated:
I use the cli wallet on Linux in a shellscript to directly make a transfer.

For example this script can invoke "./monero-wallet-cli --password=X --wallet-file=AFILENAME transfer important 11 SOMEADRESS SOME AMOUNT."

It nearly always works, but sometimes the cli wallet isn't able to make the requested transfer. The error message is then, for example, "Error: Not enough money in unlocked balance" or "Error: daemon is busy. Please try again later."

I understand the reasons, and I would like to let my shell script detect this "error". In order to do so it checks the exit code, in the "$?" pseudo-variable.

My problem is that 0 this pseudo-variable always contains 0, which means "no error".

Is it possible for the cli wallet program to exit with an adequate exit code? Ideally there would be a distinct code for each major type of error.

Globb0

legendary

Activity: 2702

Merit: 2053

Free spirit

Quote from: ballayballay on January 04, 2019, 10:42:55 PM

Quote from: dEBRUYNE on December 29, 2018, 07:12:21 AM

Do you have any suggestions for improvements then (with respect to displaying the wallet name of the currently loaded wallet)?

To facilitate bean-counting I manage 2 wallets. As the GUI doesn't always show the name of the currently loaded wallet, before any operation I have to navigate around in order to know which wallet is loaded.

My suggestion is to have the GUI display the wallet name in the upper-right zone, where it now displays a line containing the Monero logo then "Monero", and on the next line the "Balance" label. Instead of "Balance" it may display "Balance in X" where X would be the wallet name (or as much characters of the beginning of the wallet filename that can be displayed there, given the current window-size restrictions).

Thank you!

Or maybe a label you can give it a friendlier name then

ballayballay

newbie

Activity: 9

Merit: 9

Quote from: dEBRUYNE on December 29, 2018, 07:12:21 AM

Do you have any suggestions for improvements then (with respect to displaying the wallet name of the currently loaded wallet)?

To facilitate bean-counting I manage 2 wallets. As the GUI doesn't always show the name of the currently loaded wallet, before any operation I have to navigate around in order to know which wallet is loaded.

My suggestion is to have the GUI display the wallet name in the upper-right zone, where it now displays a line containing the Monero logo then "Monero", and on the next line the "Balance" label. Instead of "Balance" it may display "Balance in X" where X would be the wallet name (or as much characters of the beginning of the wallet filename that can be displayed there, given the current window-size restrictions).

Thank you!

BTCIR

newbie

Activity: 46

Merit: 0

There better not be another Monero Gold coming to the market.

Hueristic

legendary

Activity: 3836

Merit: 4969

Doomed to see the future and unable to prevent it

Quote from: florida.haunted on January 04, 2019, 11:05:45 AM

According to

https://miningpoolstats.stream/monero

XMR Network hash rate = 392.28 MH/s, while sum on all the pools = 319.24 MH/s.

The Totally Unknown hash rate is 18.6%, typical value before was 5-10%. In last weeks Totally Unknown hash rate keeps growing... ASICs?!

Probably those hybrid fpga cards finally have a bitstream for us.

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 117. (Read 4671910 times)