Armory 0.95.1 is out

[totalanni]

Armory creates an .unsigned.tx that is saved to a sd card and transfered my device to be signed.
When i go to sign it, MY device does not output logs.

I completely understand what you are saying.

[1715488685]

1715488685

[1715488685]

1715488685

[goatpig]

my device doesnt log.
It just doesnt sign anymore.

I was using this, remember.
https://bitcointalk.org/index.php?topic=870014.0

I know what you are using. My point is without logs, I can't do anything.

[FlensGold]

I have a problem installing the latest armoy version on a fresh installed Win10 Prof
Every time I try to create a new wallet the application "armoryQt.exe" does no longer work and I can only close it.
This happens after entering my passphrase the third time (Step 3: Verify Passphrase). Any idea why this happens?
Thank you

[goatpig]

Post your logs.

[FlensGold]

Post your logs.

You can find the log here.
Thank you!

[goatpig]

Delete the log, start Armory in offline mode and try again. If it fails, post the fresh log.

[FlensGold]

Delete the log, start Armory in offline mode and try again. If it fails, post the fresh log.

Here is the error screen: https://dl.dropboxusercontent.com/u/7416262/20170111%20-%20Armory%20Offline.PNG
And here come the log: https://dl.dropboxusercontent.com/u/7416262/armorylog.txt

Thank you!

[rastapopoulos]

Can I sign created transaction with this new release 0.95.1 using an offline version 0.93.3 ?

Do you plan to make an updated standalone / offline bundle, dedicated to cold storage and offline signature, compatible with a more recent OS than ubuntu 12.04 ? (like a 16.04 LTS or tails 2.9) ?

[goatpig]

2017-01-11 16:34 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe

You didn't start Armory in offline mode, it just happens to be offline because it failed to auto start bitcoind.

Let's take it from the top.

1) Make sure no instance of ArmoryDB.exe is running. If there are, just kill the process in the task manager.

2) Create a shortcut of ArmoryQt.exe. In the shortcut properties, add this to the target field:"--offline", then rename the shortcut to something like "Armory offline". Your target should look like this:

Code:

C:\Program Files (x86)\Armory\ArmoryQt.exe --offline

3) Delete your log file again, the constant RPC errors make it hard to make sense of anything.

4) Start Armory through the offline shortcut, repeat the process.

P.S: is there an ArmoryQt.exe.log file in C:\Program Files (x86)\Armory ? If so, post it.

[goatpig]

Can I sign created transaction with this new release 0.95.1 using an offline version 0.93.3 ?

Yes

Do you plan to make an updated standalone / offline bundle, dedicated to cold storage and offline signature, compatible with a more recent OS than ubuntu 12.04 ? (like a 16.04 LTS or tails 2.9) ?

I have not built any offline bundle myself. These are just carryovers from the ATI era, since I have not changed the signing code yet.

There is new signer code to cover the new address types for 0.96. This code is only active when spending from the new address types, this means you can use the old offline signers to sign for the legacy addresses funded with 0.96 and later.

If you use the new address formats, you'll need a 0.96+ signer. For that purpose I'll put out a new set of offline bundles.

Offline bundles aren't just builds however. They come with the packages needed to install Armory offline on the fresh install of the target OS. Assembling and testing the packages is a demanding task on its own, which is why you won't see offline bundles for every release, and only a few OS supported.

I use a different process than Alan for builds however. For each package, he would build the binaries directly on the target OS. I build all *nix binaries on Debian Wheezy. These binaries are compatible with everything Debian x64 based.

This leaves the question of OSes and arch. Obviously there will be at least one Ubuntu LTS. Other OSes are still up in the air atm. As for Tails, afaik they run on Debian Jessie, so a Jessie offline bundle should work, although I believe they use x86 and not x64, which is annoying in its own right.

[FlensGold]

2017-01-11 16:34 (INFO) -- ArmoryUtils.pyc:1251 - Invoked: C:\Program Files (x86)\Armory\ArmoryQt.exe

You didn't start Armory in offline mode, it just happens to be offline because it failed to auto start bitcoind.

Let's take it from the top.

1) Make sure no instance of ArmoryDB.exe is running. If there are, just kill the process in the task manager.

2) Create a shortcut of ArmoryQt.exe. In the shortcut properties, add this to the target field:"--offline", then rename the shortcut to something like "Armory offline". Your target should look like this:

Code:

C:\Program Files (x86)\Armory\ArmoryQt.exe --offline

3) Delete your log file again, the constant RPC errors make it hard to make sense of anything.

4) Start Armory through the offline shortcut, repeat the process.

P.S: is there an ArmoryQt.exe.log file in C:\Program Files (x86)\Armory ? If so, post it.

Hello,
thank you very much for this detailed explanation. I think this time the offline mode worked, but it crashes the same moment (Step 3 on creating a wallet).
Here is the log file (I overwrite it every time): https://dl.dropboxusercontent.com/u/7416262/armorylog.txt

There is no .log-file in C:\Program Files (x86)\Armory

Greetings!

Edit: If helpful I could give you Teamviewer access.

[goatpig]

I'll try to reproduce on my own, although I doubt I will manage. You are the first one to report an issue of this nature on 0.95, and there has not been significant changes in that code across versions to justify such failure.

Maybe try to run offline Armory with admin privilege, in the off case it is a permission issue.

Also teamviewer on its own won't help, as I'd need to install a whole suite of development tools to debug the issue.

P.S: Give it a try in testnet by adding --testnet to the offline shortcut target

[FlensGold]

I'll try to reproduce on my own, although I doubt I will manage. You are the first one to report an issue of this nature on 0.95, and there has not been significant changes in that code across versions to justify such failure.

Maybe try to run offline Armory with admin privilege, in the off case it is a permission issue.

Also teamviewer on its own won't help, as I'd need to install a whole suite of development tools to debug the issue.

P.S: Give it a try in testnet by adding --testnet to the offline shortcut target

Adding --testnet and starting with admin privileges does not change it: https://dl.dropboxusercontent.com/u/7416262/armorylog-testnet.txt
It only creates a subfolder "testnet3" where the log files are located.

It is a clean Win10 Prof Installation, only Windows updates so far, beside the Bitcoin Client + Armory. It is installed on a virtual machine since I only want to start it when access to my wallet is required. Win10 is also activated.

I could try another version of armory if this could help. I have an older version of armory installed on my notebook and I would like to import those wallets into this Virtual Machine once it is working.
Kind regards

[goatpig]

Are you using non ascii characters in your password? Try creating a wallet with a very simple password for testing purposes.

[FlensGold]

Are you using non ascii characters in your password? Try creating a wallet with a very simple password for testing purposes.

It happens with the password "123456" as well

If you think it could solve it a reinstall of windows would be no big thing.

[achow101]

Is the OS 32 bit or 64 bit?

Since you are using a virtual machine, you should try allocating it more than 1 core.

[goatpig]

If you think it could solve it a reinstall of windows would be no big thing.

I don't think it would achieve anything. Do you build your own binaries? I'd have you test it with 0.96

[FlensGold]

If you think it could solve it a reinstall of windows would be no big thing.

I don't think it would achieve anything. Do you build your own binaries? I'd have you test it with 0.96

No, I don't. I just downloaded the installer version from armory website

[goatpig]

Then your immediate solution is to install/VM a Debian based Linux distro to create your wallets with. Otherwise, you'll have to wait for the 0.96 testing phase to participate and help me debug the issue if it has persisted until then.

[Aurik]

Any Idea when 0.96 will be released?
A vage timeframe would be enought Informationen
like "within a month" or "somewhat between 30 and 90 days"