[BOUNTY 0.03/bug] Help test next major release of Armory! (0.91.1)

[etotheipi]

Find bugs in Armory 0.91.1, get 0.03 BTC!

This thread used to be for the 0.91 release, but I'm going to piggyback on it for for 0.91.1 because it's basically the same release, but with some minor tweaks.  Nothing substantial should've changed, except for the bug reporting and wallet-corruption handling.  This was born out of a couple reports of wallet corruption that were not being handled well by Armory in 0.91, and we had to not only improve it but add a way for users to submit their wallet recovery logs for review.  

Given that this will be pretty boring, I've upped the bounty to 0.03 BTC (~$15) per bug.  I will pay out all bounties for the original 0.91 testing and this round at the same time.  I expect this round won't be very long, and the same rules apply -- you must be the first to post it, and it must be something that isn't totally trivial.  But we're not going to be stingy about it -- we need testers more than we need to save $15 on this bounty!

This release might require explicit digging for bugs.  There might a few pieces of low-hanging fruit, but beyond that you're going to have explicitly test some of the less-commonly-used functionality (importing, sweeping, rebuilding, making & restoring backups, etc).  

  Armory 0.91.1-rc3 for Windows XP, Vista, 7, 8+ 32- and 64-bit
  Armory 0.91.1-rc3 for Ubuntu 12.04+ 32bit
  Armory 0.91.1-rc3 for Ubuntu 12.04+ 64bit
  Armory 0.91.1-rc3 for Raspbian armhf
  Armory 0.91.1-rc3 for MacOSX 10.7+ 64bit


  Armory 0.91.1-rc3 Offline Bundle for Ubuntu 12.04 32bit
  Armory 0.91.1-rc3 Offline Bundle for Ubuntu 12.04 64bit
  Armory 0.91.1-rc3 Offline Bundle for Raspbian (armhf)

  Armory 0.91.1-rc3:  Signed hashes of all installers

Note:  The RPi regular build works just fine (as far as I can tell).  However the RPi offline bundle is still a work in progress.  No guarantees it works for as advertised!



---- ORIGINAL 0.91 TESTING DESCRIPTION ----

We finally have a stable version of what is soon to become Armory 0.91-beta.  We just put out a testing release (link below) and want to encourage people to help test by offering coins for your time. We are aware of a few quirks with the latest version, but nothing serious, all just usability/convenience/interface issues.  We will pay out for the obvious ones, as long as you're the first!

https://bitcointalk.org/index.php?topic=522866.0

See post above for details on the new version.  Here's a few highlights:
-- Major fix for 99%-scanning crashing bug, and general performance improvements
-- Solid OSX support including 10.9.1 and 10.9.2 (we think!)
-- Torrent download for initial network sync (only in auto-bitcoind mode)
-- New announcement system and secure downloader
-- Binaries for RaspberryPi (armhf)!


All bounty payout decisions are final!  We're not going to be stingy about bounties, but we do have to be reasonable.  We have done this in the past and no one complained.  Let's keep it up!

[1713443983]

1713443983

[1713443983]

1713443983

[1713443983]

1713443983

[qnxt]

Not sure if this counts as a bug in Armory itself...but the OS X tarfile gives a 403 error.

--2014-03-30 20:12:26--  https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.5-testing_osx.tar.gz
Resolving s3.amazonaws.com... 176.32.97.242
Connecting to s3.amazonaws.com|176.32.97.242|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2014-03-30 20:12:26 ERROR 403: Forbidden.

I also can't download it from within 0.90.99.4, because it crashes when I try to use the secure downloader.

I can download all other versions fine from the urls in your other post. Please chmod the OS X version.

[etotheipi]

Not sure if this counts as a bug in Armory itself...but the OS X tarfile gives a 403 error.

--2014-03-30 20:12:26--  https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.5-testing_osx.tar.gz
Resolving s3.amazonaws.com... 176.32.97.242
Connecting to s3.amazonaws.com|176.32.97.242|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2014-03-30 20:12:26 ERROR 403: Forbidden.

I also can't download it from within 0.90.99.4, because it crashes when I try to use the secure downloader.

I can download all other versions fine from the urls in your other post. Please chmod the OS X version.

It was actually a bad filename.  I just updated the post on the testing thread with the correct link.

[qnxt]

Minor cosmetic error. On first opening 0.90.99.5, I'm presented with an out-of-date notice:

"New Testing Version 0.90.99.5
You are using version 0.90.99.5"

The announcements tab does show that I'm using the latest version under "Software Version Updates".

Edit: And another minor problem with the OS X download. I tried using the "secure downloader" to grab the same version. But it also has the url with "osx" instead of "OSX" in the filename. That's obviously not much of an issue, but it doesn't handle the 403 error correctly: it tells me that the download completed, but that the signature was invalid. (When it didn't actually download anything.)

The secure downloader also fails to detect my OS at all (OS X 10.9.2), giving me a warning then letting me manually select.

[etotheipi]

I just explicitly tested the version check, and I didn't get a notification on 0.90.99.5.  Apparently I did something wrong.  Will have to check that it's respecting the min/max versions in the notifications.

As for it failing to download the OSX version, I was using an outdated announcement file when renaming the downloads.  Whoops.  Will be fixed in a minute (just going to put two copies there, one with each name).

[qnxt]

Another cosmetic bug...if I select "Use an existing address for change", the text above becomes squished and unreadable.

It almost looks like I blanked it myself for security, but I didn't!

https://i.imgur.com/xv3S2RO.png

Also on that screen: when I use the + or - Recipient buttons, the list resets to the top. Not really a big deal, but it'll make adding a bunch of addresses annoying, scrolling down for each one.

I haven't found any functional bugs yet, which is good!

Edit: Another nitpick. The About box lists the copyright date as 2011-2013. Shouldn't that be 2011-2014?

[george51]

https://i.imgur.com/MIi6tbe.jpg

This may only be a small bug - It says its out-of-date when I've got the most recent version. Also when I downloaded it - and selected my OS (windows 8.1) there was no option to select the new version.

[ncs0ne]

I cannot export transactions any more.

I tried "Help-> Rebuild and Rescan Databases" with a restart afterwards as well, but it doesn't help.
btw: I'm deeply impressed by the startup speed increase 

Code:

2014-03-31 12:50 (ERROR) -- Traceback (most recent call last):
  File "/usr/lib/armory/qtdialogs.py", line 8778, in accept
    if self.createFile_CSV():
  File "/usr/lib/armory/qtdialogs.py", line 8856, in createFile_CSV
    f.write('Export Date:, %s\n' % unixTimeToFormatStr(RightNow()))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 20: ordinal not in range(128)

[idoB]

UI Issue:
when generating new receive address and choosing 'create clickable link' - the resulting form is cut out at the top and the only way I can get it to fully display is by resizing it - it then pops down and displays correctly. For example:

[Brangdon]

It was actually a bad filename.  I just updated the post on the testing thread with the correct link.

It's also wrong in the Secure Downloader for Windows, I think.

I got an announcement in Armory itself, which led to the Help/Update Armory dialog. 0.90.99.5 is listed for WinXP, Vista, Win7 and Win8, both 32-bit and 64-bit, but none of them actually work. It's not listed at all for Win8.1.

Edit: I've now downloaded manually from the link. I notice that the installer defaulted to C:, rather than the location I the previous Armory is at, which is D:. Is that intentional?

[Brangdon]

(1) The scroll bars on the dashboard message have a problem. When I try to scroll down, it jumps back up. I think it wants to keep the "Armory is offline" message visible at the top.

This is on WinXP - it installs and works there now. My screen on that machine is only 600 pixels high, so without the scroll bars I can't read the rest of the message. My Win8.1 install doesn't have this issue, not even if I make the Dashboard window small. However, it is online, so it's displaying a different message.

(2) My Win8.1 Armory thinks it is online despite not having an internet connection - is that correct? It is running Bitcoin Core and has synchronised blocks etc, but won't be seeing new transactions and probably won't be broadcasting them either, because I've disabled my network adaptor. I can't access Google. I guess that the internet part is done by Bitcoin Core, so Armory doesn't know its status, but it's a bit confusing to be told it is online when it isn't.

[etotheipi]

(1) The scroll bars on the dashboard message have a problem. When I try to scroll down, it jumps back up. I think it wants to keep the "Armory is offline" message visible at the top.

This is on WinXP - it installs and works there now. My screen on that machine is only 600 pixels high, so without the scroll bars I can't read the rest of the message. My Win8.1 install doesn't have this issue, not even if I make the Dashboard window small. However, it is online, so it's displaying a different message.

(2) My Win8.1 Armory thinks it is online despite not having an internet connection - is that correct? It is running Bitcoin Core and has synchronised blocks etc, but won't be seeing new transactions and probably won't be broadcasting them either, because I've disabled my network adaptor. I can't access Google. I guess that the internet part is done by Bitcoin Core, so Armory doesn't know its status, but it's a bit confusing to be told it is online when it isn't.

Whoops, we forgot to fix the dashboard scrolling thing.  Definitely a bounty for that one.  Also ,I stupidly didn't include Windows 8.1 in the new download list, even though it should be included.  We plan to remove the OS sub-version fields in the future, and have a better system for linking downloads to OS.  But this version will keep it, for now. 

Not sure what's up with the download links.  I just tested it on my system and can download Windows installers fine.  Can you make sure you have the latest announcments by clicking the "Check for Updates" button on the "Announcements" tab?

As for where it's installed... that's good point we haven't thought about.  The installer should probably detect where the previous installation is and default to that.  Not sure how to do it but we can look into it.

[donut]

Secure Downloader bug: There is no 64-bit version available for Windows 8.1 (but everything is available for 8):

https://i.imgur.com/WtLQuuJ.png

Also, it couldn't detect the fact that I have Windows 8.1 x64 for some reason.


It complains about the version being "outdated" on every startup and offers to upgrade... to the same version.

[etotheipi]

Okay, so far we have in the queue for fixing:

• Auto-detect OS in secure downloader
• Respect version-range of notifications w.r.t to current version
• Add Windows 8.1 to the next notification set
• Dashboard scroll-reset issue when in offline mode
• Export transactions to CSV needs to work with unicode
• Update "About" window with proper copyright years
• Fix bug-reporting URLs and certificates
• Add urllib3 library to Windows build
• Show appropriate message on Secure-Downloader 403 error (currently shows failed sig error, should be URL-not-avail message)
• Fix filenames in offline signing script to avoid upload issues again

This is not a tally of bounties.  Most things that were reported first will get a bounty.  This is just  a list/summary of things we can fix for the next testing release.

@testers:  also, some other features to test:
-- Send to P2SH address
-- Download blockchain via torrent (just set a new --datadir and --satoshi-datadir and it should jump right into it)
-- Restore wallet from backup over existing
-- Fix corrupted wallets (if you have any)

[Brangdon]

Not sure what's up with the download links.  I just tested it on my system and can download Windows installers fine.  Can you make sure you have the latest announcments by clicking the "Check for Updates" button on the "Announcements" tab?

Yep. "Check for Updates" says they are up to date, but Secure Downloader still says "There was a failure downloading this file: 0" when I try "Armory testing (unstable)"

Also I note there are no release notes for it.

[etotheipi]

Not sure what's up with the download links.  I just tested it on my system and can download Windows installers fine.  Can you make sure you have the latest announcments by clicking the "Check for Updates" button on the "Announcements" tab?

Yep. "Check for Updates" says they are up to date, but Secure Downloader still says "There was a failure downloading this file: 0" when I try "Armory testing (unstable)"

Also I note there are no release notes for it.

Can you try clicking on "Download Info" and copy the URL into your browser and see if it downloads it?  I'm not sure why it's having an issue.  It sounds like a different error than simply not existing, which as noted in my previous post, gives an "Invalid Signature" error.

[Brangdon]

Should "Review Offline Transaction" show more information?

I've now created an offline wallet, sent some coins to it, created a transaction on my desktop, signed it with the offline machine, and broadcast it with the online machine. It all seems to work OK. However, I noticed that the dialog to review the transaction before signing or broadcasting seems to be missing information. There's nothing for the "Wallet:" or even the "Transaction Amount:", although those should surely be known. Also, clicking for "more information about this transaction" did nothing. The dialog after "Sign" or "Broadcast" did show some information, including the transaction amount.

[Brangdon]

Can you try clicking on "Download Info" and copy the URL into your browser and see if it downloads it?

That downloaded OK. That URL seems to be the same as in the first post in the download thread.

---------------------------
Package Information
---------------------------
Download information for <b>ArmoryTesting version 0.90.99.5:</b> <br> <ul> <li><u><b>Operating System</b></u>:</li> <ul> <li>Windows 8 64-bit</li> </ul> <li><u><b>Installer Filename</b></u>:</li> <ul> <li>armory_0.90.99.5-testing_winAll.exe</li> </ul> <li><u><b>Download URL</b></u>:</li> <ul> <li>https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.90.99.5-testing_winAll.exe</li> </ul> <li><u><b>Verified sha256sum</b></u>:</li> <ul> <li>9b5a76cdb28b7cb8f5bd3446646f018d30394994330a995fd979db9b4e72c1bc</li> </ul> </ul>
---------------------------
OK  
---------------------------

[escrow.ms]

Tried it on Windows 8.1 64 Bit, didn't found any bugs except some small errors.

Step-4 UI is little bit messed up
https://i.imgur.com/65MO2PK.png

There's no Armory 0.90 Download in windows 8.1
https://i.imgur.com/aeJmDga.png


I tried to recover a unencrypted backup wallet just for testing and it said "99 errors where found"


Errors were about chain index
http://pastie.org/8983553


Ps: Torrent download works great.
https://i.imgur.com/R2Xv41b.png
https://i.imgur.com/XKNKnDB.png

[Brangdon]

I just failed to send some coin to three addresses. It got as far as asking for my password, but when I clicked Unlock it returned to the "Sending from Wallet" dialog. There was no error message. I'm pretty sure I had the right password (and if I hadn't, I'd expect a helpful error message saying as much). I tried again after deleting the last address, and that failed the same way. I then deleted another address, so that only one was left, and that succeeded as expected.

(This was all on my desktop; no offline signing shenanigans involved.)

[goatpig]

Tried it on Windows 8.1 64 Bit, didn't found any bugs except some small errors.

Step-4 UI is little bit messed up
https://i.imgur.com/65MO2PK.png

There's no Armory 0.90 Download in windows 8.1
https://i.imgur.com/aeJmDga.png


I tried to recover a unencrypted backup wallet just for testing and it said "99 errors where found"


Errors were about chain index
http://pastie.org/8983553


Ps: Torrent download works great.
https://i.imgur.com/R2Xv41b.png
https://i.imgur.com/XKNKnDB.png

Most likely a non sequential address entry order. This alone doesn't constitute an error. It's a clue in case other errors occurred though.

I just failed to send some coin to three addresses. It got as far as asking for my password, but when I clicked Unlock it returned to the "Sending from Wallet" dialog. There was no error message. I'm pretty sure I had the right password (and if I hadn't, I'd expect a helpful error message saying as much). I tried again after deleting the last address, and that failed the same way. I then deleted another address, so that only one was left, and that succeeded as expected.

(This was all on my desktop; no offline signing shenanigans involved.)

Fixed this error this morning. Will be part of the next testing build

[goatpig]

I cannot export transactions any more.

I tried "Help-> Rebuild and Rescan Databases" with a restart afterwards as well, but it doesn't help.
btw: I'm deeply impressed by the startup speed increase 

Code:

2014-03-31 12:50 (ERROR) -- Traceback (most recent call last):
  File "/usr/lib/armory/qtdialogs.py", line 8778, in accept
    if self.createFile_CSV():
  File "/usr/lib/armory/qtdialogs.py", line 8856, in createFile_CSV
    f.write('Export Date:, %s\n' % unixTimeToFormatStr(RightNow()))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 20: ordinal not in range(128)

Should be fixed for 0.90.99.6

[japandrew73]

I just downloaded the newest version and believe I've found a bug.  I'm running Armory on a 2010 MacBook Pro with Mavericks 10.9.2.

Every time I try to open the application, it jumps up and down on my dock and then force-quits itself.  I am never actually able to fully open the app.  I noticed this error was occurring on the previous version as well.  I have a desire to use Armory but am currently forced to use Electrum due to their OSX support with the latest version of Mavericks. 

I really hope you guys can fix this bug so I can open Armory and switch over from Electrum!

[CircusPeanut]

Should "Review Offline Transaction" show more information?

I've now created an offline wallet, sent some coins to it, created a transaction on my desktop, signed it with the offline machine, and broadcast it with the online machine. It all seems to work OK. However, I noticed that the dialog to review the transaction before signing or broadcasting seems to be missing information. There's nothing for the "Wallet:" or even the "Transaction Amount:", although those should surely be known. Also, clicking for "more information about this transaction" did nothing. The dialog after "Sign" or "Broadcast" did show some information, including the transaction amount.

Good find Brangdon. I can reproduce this issue (or one like it) in my debugger.

[etotheipi]

I just downloaded the newest version and believe I've found a bug.  I'm running Armory on a 2010 MacBook Pro with Mavericks 10.9.2.

Every time I try to open the application, it jumps up and down on my dock and then force-quits itself.  I am never actually able to fully open the app.  I noticed this error was occurring on the previous version as well.  I have a desire to use Armory but am currently forced to use Electrum due to their OSX support with the latest version of Mavericks. 

I really hope you guys can fix this bug so I can open Armory and switch over from Electrum!

Hey japandrew73,

If Armory is bouncing on the dock, that's a good sign -- at least it's trying to open, and probably left us some useful messages in the log file.  If you simply double-clicked it without any command-line args, etc, then it created a log file in

~/Library/Application Support/Armory/armorylog.txt

Could you either post the contents, or just the end of it?

[CircusPeanut]

I just failed to send some coin to three addresses. It got as far as asking for my password, but when I clicked Unlock it returned to the "Sending from Wallet" dialog. There was no error message. I'm pretty sure I had the right password (and if I hadn't, I'd expect a helpful error message saying as much). I tried again after deleting the last address, and that failed the same way. I then deleted another address, so that only one was left, and that succeeded as expected.

(This was all on my desktop; no offline signing shenanigans involved.)

I am unable to reproduce this bug. If you can make it happen again, please do so, export the log file (using the File menu), and send it to us here: https://bitcoinarmory.com/support/

[etotheipi]

I just failed to send some coin to three addresses. It got as far as asking for my password, but when I clicked Unlock it returned to the "Sending from Wallet" dialog. There was no error message. I'm pretty sure I had the right password (and if I hadn't, I'd expect a helpful error message saying as much). I tried again after deleting the last address, and that failed the same way. I then deleted another address, so that only one was left, and that succeeded as expected.

(This was all on my desktop; no offline signing shenanigans involved.)

I am unable to reproduce this bug. If you can make it happen again, please do so, export the log file (using the File menu), and send it to us here: https://bitcoinarmory.com/support/

I'm pretty sure that goatpig already fixed this.   You probably don't see it because you've already pulled the fix that he pushed.

[TheAwer]

I have a feeling that the "Scanning Transaction History" time remaining counter should be counting down, not up.  It's been more than 30 minutes since I opened Armory and it has gone from 27 to 30 minutes remaining.

On the other hand, at least I can open the new Armory on my Mac!

[Raize]

Most likely a non sequential address entry order. This alone doesn't constitute an error. It's a clue in case other errors occurred though.

I think he's talking about the grammatical error though. "Were found" vs. "Where found".

[moug]

I have a feeling that the "Scanning Transaction History" time remaining counter should be counting down, not up.  It's been more than 30 minutes since I opened Armory and it has gone from 27 to 30 minutes remaining.

On the other hand, at least I can open the new Armory on my Mac!

I had same thing happen it said 1 hour then 30 minutes then 1 hours then 100,99,98 blocks, I should have
recorded all this but went to sleep, but it is working.

XP SP3 2G ram.

Once it's up to date it could say some thing like OK or a green check mark, in the dashboard.

How do I insert a image .jpg file?

[goatpig]

Most likely a non sequential address entry order. This alone doesn't constitute an error. It's a clue in case other errors occurred though.

I think he's talking about the grammatical error though. "Were found" vs. "Where found".

Yes, I realized that only later and facepalmed. I reduced the verbose on that particular kind of error anyway.

I have a feeling that the "Scanning Transaction History" time remaining counter should be counting down, not up.  It's been more than 30 minutes since I opened Armory and it has gone from 27 to 30 minutes remaining.

On the other hand, at least I can open the new Armory on my Mac!

I had same thing happen it said 1 hour then 30 minutes then 1 hours then 100,99,98 blocks, I should have
recorded all this but went to sleep, but it is working.

XP SP3 2G ram.

Once it's up to date it could say some thing like OK or a green check mark, in the dashboard.

How do I insert a image .jpg file?

The ETA calculation is a little wacky. It estimates progress linearly when newer blocks are generally harder to parse. It's among the things I'm working on so I'll get to it eventually.

Not that, it's wacky, simply because it's hard to estimate. Will still try to find something better.

[windpath]

Had an "Armory is out of date" notice on first run on OSX, then it goes away.

[TheAwer]

Had an "Armory is out of date" notice on first run on OSX, then it goes away.

I had that too.

EDIT: except it comes back on each restart.

[goatpig]

Known issue. Trying out the new notifier feature, we got a little aggressive. Should be fixed for 0.90.99.6

[Natanael]

Another 99% crash.

http://imgur.com/XdpxWRy

[goatpig]

Another 99% crash.

http://imgur.com/XdpxWRy

Did you wipe your previous DB before building with 0.90.99.5?

[TheAwer]

I have an issue with the transaction log on OSX.  In the previous version, I received bitcoin, sent some, received some more, and then sent it all out.

I forget what the transaction log looked like in the previous version, but after I installed the new beta the last transaction is missing under the transactions log.  The balance is shown as 0.00, but under transactions there are only my first three transactions, not the latest one that emptied my wallet. 

Transaction 1: +0.145259
Transaction 2: -0.1001
Transaction 3: +0.064
Transaction 4: empties wallet, but not shown under transactions.

[japandrew73]

I just downloaded the newest version and believe I've found a bug.  I'm running Armory on a 2010 MacBook Pro with Mavericks 10.9.2.

Every time I try to open the application, it jumps up and down on my dock and then force-quits itself.  I am never actually able to fully open the app.  I noticed this error was occurring on the previous version as well.  I have a desire to use Armory but am currently forced to use Electrum due to their OSX support with the latest version of Mavericks. 

I really hope you guys can fix this bug so I can open Armory and switch over from Electrum!

Hey japandrew73,

If Armory is bouncing on the dock, that's a good sign -- at least it's trying to open, and probably left us some useful messages in the log file.  If you simply double-clicked it without any command-line args, etc, then it created a log file in

~/Library/Application Support/Armory/armorylog.txt

Could you either post the contents, or just the end of it?

It ended up working after all.  The first time I booted the app from the desktop but when I moved it to my applications folder it opened properly and working great!

I have the previous version of Armory running on my Raspberry Pi offline.  The version that wallet was created on shouldn't conflict at all with the version I'm running on my Mac should it?  Seems like it wouldn't be an issue if I'm running a "watch-only" wallet on my Macbook anyways.

[moug]

OK
I did have a big problem with XP SP3 and 2G ram.

I had it running for ~1 day with Utorrent and Firefox(watching video), and some how ALL of my hard drive was used up!
So I checked and my bitcoin dir was ~18 GB and Armory ~20 GB what I failed to do was check the memory
file size. It was set to auto on that drive. I never had that problem before! and some "unknown" IP's on
active ports program.

I rebooted and changed the "system managed size" to a fixed size 4096.
And my drive had ~76 GB free space back.

And it's working again on XP SP3 2 GB ram. not looking for bounty.
I do have a pdf of screen shot's of when it's started, to when it up to date how to send?

[goatpig]

I have an issue with the transaction log on OSX.  In the previous version, I received bitcoin, sent some, received some more, and then sent it all out.

I forget what the transaction log looked like in the previous version, but after I installed the new beta the last transaction is missing under the transactions log.  The balance is shown as 0.00, but under transactions there are only my first three transactions, not the latest one that emptied my wallet. 

Transaction 1: +0.145259
Transaction 2: -0.1001
Transaction 3: +0.064
Transaction 4: empties wallet, but not shown under transactions.

Known ledger issue, fixed for 0.90.99.6

OK
I did have a big problem with XP SP3 and 2G ram.

I had it running for ~1 day with Utorrent and Firefox(watching video), and some how ALL of my hard drive was used up!
So I checked and my bitcoin dir was ~18 GB and Armory ~20 GB what I failed to do was check the memory
file size. It was set to auto on that drive. I never had that problem before! and some "unknown" IP's on
active ports program.

I rebooted and changed the "system managed size" to a fixed size 4096.
And my drive had ~76 GB free space back.

And it's working again on XP SP3 2 GB ram. not looking for bounty.
I do have a pdf of screen shot's of when it's started, to when it up to date how to send?

Unknown IPs are from Bitcoin core peer connections. As for Windows, the cluster size should remain 4096.

[qnxt]

0.90.99.5 pegs one CPU core on OS X when anything besides the main window is open. This happens with Send Bitcoins, Receive Bitcoins, Wallet Properties, Offline Transactions, and even the About box.

It drops back down after 1 - 2 minutes of being idle in the background, but that appears to be due to App Nap. If I get info on the app and disable App Nap, then Armory eats CPU indefinitely. (Or if I leave it in the foreground.)

9553   Python       99.2 01:44:17 8/1  1    156-  2265   286M-  797M+  0B     17M    2021M  4556M  9549  9549  running  501

ps output over 5 minutes after clicking Receive Bitcoins, then letting it sit at "Select Wallet" in the background:

Wed Apr  2 20:41:01 EDT 2014
x         29597  99.0  6.0  3739228 503900   ??  R     8:34PM   5:16.55 /Applications/Armory.app/Contents/MacOS/Python /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py

Wed Apr  2 20:46:02 EDT 2014
x         29597  60.7  6.0  3849040 507088   ??  R     8:34PM  10:07.81 /Applications/Armory.app/Contents/MacOS/Python /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py

Armory is still pretty responsive for me even when it's doing that (much more than 0.90.99.4), and if I go back to the main window, CPU usage drops back down. (It only used about 2 or 3 seconds of CPU time over 5 minutes at the main window.) I have a total of 4 wallets with around 100 addresses and 200 transactions.

Edit: Still happening in 0.90.99.7.

[Natanael]

Another 99% crash.

http://imgur.com/XdpxWRy

Did you wipe your previous DB before building with 0.90.99.5?

Not yet, will try.

[goatpig]

I accidentally reverted the 99% fix in 0.90.99.5. Wait for .6 for the fix of the fix =P

[TheAwer]

Another thing: I had Armory open when Bitcoin Core was catching up, and Armory was updating the database (or whatever it does).  I got a notification that Armory was online and had finished loading, but when I checked Bitcoin Core there were still 13 hours to catch up on.  After I clicked the close button (or whatever the okay button is called), Armory froze.  It's still frozen now.

EDIT: It unfroze.  Also, in the bottom right, it says "Connected (0 blocks)", if that's any help.

EDIT EDIT: I restarted and it worked fine.

[goatpig]

Another thing: I had Armory open when Bitcoin Core was catching up, and Armory was updating the database (or whatever it does).  I got a notification that Armory was online and had finished loading, but when I checked Bitcoin Core there were still 13 hours to catch up on.  After I clicked the close button (or whatever the okay button is called), Armory froze.  It's still frozen now.

EDIT: It unfroze.  Also, in the bottom right, it says "Connected (0 blocks)", if that's any help.

EDIT EDIT: I restarted and it worked fine.

The current Armory model doesn't play so nice with a heavily back tracked Bitcoin Core. Ideally you want to either automanage bitcoind, in which case Armory will make sure bitcoind is fully sync'd before processing further, or let BitcoinQt sync before running Armory.

This may change in the future, as the model is getting overhauled.

[japandrew73]

Overall after testing with OSX 10.9.2 running offline transactions from my Pi, I'd say you guys did some pretty great work with this last release!

Great job

[Brangdon]

I'm pretty sure that goatpig already fixed this.

It is indeed fixed in 0.91-beta. (At least, it let me send to two addresses; I didn't try three.)

Do you want updates on what other bugs are or aren't fixed in this version?

[goatpig]

I'm pretty sure that goatpig already fixed this.

It is indeed fixed in 0.91-beta. (At least, it let me send to two addresses; I didn't try three.)

Do you want updates on what other bugs are or aren't fixed in this version?

sure, keep 'em coming

[jl2012]

In "Update Software", it fails to determine Windows Server 2012 R2, which should be equivalent to Windows 8

[veyp0r]

Hi,

Is source code available for this release? I found a few binaries/packages , but there doesn't seem to be anything on GitHub matching this release number.

Thanks!

[jl2012]

This is not a new bug but is not get fixed. I can import 0000000000000000000000000000000000000000000000000000000000000000 as private key (which is invalid), and the address will be shown as 16QaFeudRUt8NYy2yzjm3BMvG4xBbAsBFM. When I try to spend the bitcoin in that address, Armory crashed.

[qnxt]

So...you guys closing out the bounties since 0.91 is out?

[etotheipi]

So...you guys closing out the bounties since 0.91 is out?

Sorry for the delay... I totally got swamped and forgot about the bounties.  I will compile a list of first-reported bugs and then have people PM their addresses to me.

However, we're about to do a 0.91.1 release with some tweaks and notifications regarding corrupt wallet reports.  Unless I hear complaints... I would like to just merge it all into one bounty campaign and pay out all at once.  Since the changed in this point release are so minimal and isolated, it should be a very quick testing phase

[etotheipi]

(updated top post and copied here)


Find bugs in Armory 0.91.1, get 0.03 BTC!

This thread used to be for the 0.91 release, but I'm going to piggyback on it for for 0.91.1 because it's basically the same release, but with some minor tweaks.  Nothing substantial should've changed, except for the bug reporting and wallet-corruption handling.  This was born out of a couple reports of wallet corruption that were not being handled well by Armory in 0.91, and we had to not only improve it but add a way for users to submit their wallet recovery logs for review. 

Given that this will be pretty boring, I've upped the bounty to 0.03 BTC (~$15) per bug.  I will pay out all bounties for the original 0.91 testing and this round at the same time.  I expect this round won't be very long, and the same rules apply -- you must be the first to post it, and it must be something that isn't totally trivial.  But we're not going to be stingy about it -- we need testers more than we need to save $15 on this bounty!

This release might require explicit digging for bugs.  There might a few pieces of low-hanging fruit, but beyond that you're going to have explicitly test some of the less-commonly-used functionality (importing, sweeping, rebuilding, making & restoring backups, etc). 

https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_32bit.deb
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_64bit.deb
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_osx.tar.gz
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_raspbian.tar.gz
https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_winAll.exe

Due to my build scripts breaking I wasn't able to go through the official release process for the testing build.  So I have signed the hashes with my regular GPG key (not the offline key).  While this is in testing, I'll be rewriting the build & release scripts and everything will be done properly by the time we actually release.

https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc1_sha256.txt.asc

[Corelianer]

Thank you for the great improvements especially the security allert system and the torrent downloader.

UI:
- A cosmetic uglyness: Windows 7 64Bit. When you open the settings the window upens so that you have also a vertical scroll-bar.


Secure Downloader:
- Armory could not find an appropriate download for your operating system. You have to manually select the correct download on the next window.

Debug Log:
- The debug log says "System is 64-bit      : False". But my system is indeed Windows 64-Bit. (Maybe because the ArmoryQt.exe is a 32-bit application?)

Torrent Download:
- How can I find out if the torrent download is working and at what speed? Is it only downloading or also seeding?

Wallet Creation Wizard:
- Creating a password with just 5 letters is possible and I'm not warned that my password would be very-weak.


Paper Backup:
- Frame is overlapping with the Root-Key in the preview as well as in the printout (FYI the printscreen is from a empty wallet, no bitcoins to steal )

[qnxt]

No problem; merging them makes sense.

I can't even open 0.91.1 on OS X 10.9.2 due to a library issue. Just closes immediately when I double-click, and if I launch it manually:

/Applications/Armory.app/Contents/MacOS$ ./Armory
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/ArmoryQt.py", line 34, in <module>
    from armoryengine.ALL import *
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ALL.py", line 1, in <module>
    from armoryengine.ArmoryUtils import *
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ArmoryUtils.py", line 39, in <module>
    from CppBlockUtils import KdfRomix, CryptoAES
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/CppBlockUtils.py", line 28, in <module>
    _CppBlockUtils = swig_import_helper()
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/CppBlockUtils.py", line 24, in swig_import_helper
    _mod = imp.load_module('_CppBlockUtils', fp, pathname, description)
ImportError: dlopen(/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/_CppBlockUtils.so, 2): Symbol not found: __ZTVN8CryptoPP18StringSinkTemplateISsEE
  Referenced from: /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/_CppBlockUtils.so
  Expected in: flat namespace
 in /Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/_CppBlockUtils.so

[etotheipi]

About OSX: 

Looks like the package didn't get fully recompiled.  I just wiped the mac directory and then recompiled from scratch (which takes forever, btw).  let me know if this works better:

https://s3.amazonaws.com/bitcoinarmory-testing/armory_0.91.1-rc2_osx.tar.gz


About Raspberry Pi:

I finally got my RPi up and was able to collect the dependency tree.  Bundled it up into a tar.gz.  You should be able to copy that to the RPi and "sudo dpkg -i *.deb" from the unpacked tar.gz directory.  After that, you should be able to simply unpack the tar.gz and run Armory.  Please try it:

https://s3.amazonaws.com/bitcoinarmory-testing/armory_raspbian_deps.tar.gz


@Corelianer:

Thanks for all the reports.  Admittedly, a couple things (like password length and complexity) is a design design decision, not a bug.  I'll look more closely at what you put there, and might consider a couple trivial things to be worth one bounty together.  I'll let you know soon, and you can appeal appropriately

If it is using torrent, it is very explicit:  the main window will show you "Synchronizing using Armory CDN" and it will tell you download speed and number of peers.  Uploading is disabled -- we are running about 30 seedboxes to make up for that.  Based on some conversations on the Bitcoin mailing list, this may be obsolete soon, as the core devs seemed to have figured out how to make P2P synchronization just as fast (though it'll probably be like 6 months before it actually gets into Bitcoin core).

[KaChingCoinDev]

Issue:

Downloader is 0.9.0 for Bitcoin. Bitcoin is on 0.9.1, 0.9.0 had bad OpenSSL. Screenshot:




I don't know if it qualifies as a bug, but here is my BTC addy:
1Pi7AD6hUw3SBbFR5bPxxiZ6cH5hBF4fSM

[etotheipi]

Issue:

Downloader is 0.9.0 for Bitcoin. Bitcoin is on 0.9.1, 0.9.0 had bad OpenSSL. Screenshot:

<img>


I don't know if it qualifies as a bug, but here is my BTC addy:
1Pi7AD6hUw3SBbFR5bPxxiZ6cH5hBF4fSM

I'll give it to you because technically you're right  Updating that download was going to be part of this release you're testing right now!  It's not critical because the way Armory runs bitcoind 0.9.0 does not expose the OpenSSL bug.  

[KaChingCoinDev]

Issue:

Downloader is 0.9.0 for Bitcoin. Bitcoin is on 0.9.1, 0.9.0 had bad OpenSSL. Screenshot:

<img>


I don't know if it qualifies as a bug, but here is my BTC addy:
1Pi7AD6hUw3SBbFR5bPxxiZ6cH5hBF4fSM

I'll give it to you because technically you're right  Updating that download was going to be part of this release you're testing right now!  It's not critical because the way Armory runs bitcoind 0.9.0 does not expose the OpenSSL bug.  

Thanks   Let me know when you send the coins

[qnxt]

The copyright date in the about box is still 2011-2013 instead of 2011-2014, even though I think I saw that acknowledged when I reported it before. Version number was updated, just not the year.

A couple other minor ones:

https://i.imgur.com/lDQjGBU.png
Shows under announcements under All Available Notifications, which is a little confusing, but pretty trivial.

Reported this one before, just cosmetic since I can resize to fix it (but that's not obvious). It happens after I select "Use an existing address for change":
https://i.imgur.com/1sG72lJ.png

(Edit: And rc2 does work on OS X; thanks.)

[qnxt]

After performing a consistency check, it gets stuck on the dialog with the menu options all grayed out. I can drag the window around, just not do anything, and ended up having to kill the Python process. This occurs for recoveries too, not just consistency checks (tested with a couple other options from "Fix Damaged Wallet" and it did the same.)

https://i.imgur.com/Uufq57P.png

According to the wallet recovery log, it succeeded. "armorylog.txt" contains the following error:

2014-04-27 21:52 (ERROR) -- ArmoryUtils.py:2786 - Error in pybkgdthread: setRecoveryDone() takes exactly 5 arguments (4 given)
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ArmoryUtils.py", line 2784, in run
    self.output = self.func()
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ArmoryUtils.py", line 2721, in funcPartial
    return thefunc(*args, **kwargs)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/PyBtcWalletRecovery.py", line 1867, in ParseWallet
    dlg.setRecoveryDone(wlterror, goodWallets, fixedWlt)
TypeError: setRecoveryDone() takes exactly 5 arguments (4 given)

Edit: File->Minimize Armory hides the window...permanently. (OS X still.) Couldn't figure out how to make it reappear without quitting and relaunching. (Edit again: It hides the main window, not the stuck consistency check window, to clarify. Menu items are grayed out for the stuck window, so Minimize wouldn't even be an option. So these are unrelated bugs.)

[KaChingCoinDev]

BTC not arrived yet

No rush, just letting you know

[etotheipi]

BTC not arrived yet

No rush, just letting you know

Was going to collect all bug reports and distribute once 0.91.1 is released.  If you are anxious, I can send to you now.  But I'll do a batch send for everyone when this is done.

[KaChingCoinDev]

BTC not arrived yet

No rush, just letting you know

Was going to collect all bug reports and distribute once 0.91.1 is released.  If you are anxious, I can send to you now.  But I'll do a batch send for everyone when this is done.

Noooo problem. Just making sure.

[Corelianer]

What about possibility to change the language of Armory?

I could assist translating from English to German.

[drips]

Bug 1:

Fixed in rc2, missed that further down the topic.


Bug 2:

https://i.imgur.com/cvjUU2w.jpg

The option for "don't do a online check" and "disable updates" doesn't seem to actually work. An outgoing connection is made anyway.


Bug 3:

https://i.imgur.com/Ka8Z2xN.jpg

It's impossible to close the "wallet consistency check" dialogue on Windows, the window jumps to the front and can't be closed by right clicking or with the close button.


Bug 4:

https://i.imgur.com/LhjGnFu.jpg

On windows the "backup wallet" dialogue text is smushed when creating a new wallet, but not when clicking the "backup" button in the wallet properties area.



Bug 5:

https://i.imgur.com/4ZzJ4VI.jpg

https://i.imgur.com/Ek79dZw.jpg


The "address book" icon in the message signing window is hidden by the window being too small. Expanding the window again allows it to be seen and used, but it's invisible and un-findable otherwise.


Bug 6:

https://i.imgur.com/QkaDCwZ.jpg

The "create clickable link" window is spawned above the top of the screen and is fairly useless as a result. Worked the first time but subsequent ones failed in the manor shown.


Bug 7:

Code:

/Applications/Armory.app/Contents/MacOS/Armory: line 23: 39855 Segmentation fault: 11  $DIRNAME/Python $ARMORYDIR/ArmoryQt.py

Clicking around the "wallet properties" area on OSX (sorting, opening addresses, closing windows, payment requests) often causes a segfault, though I can't find a reliable trigger other than random exploration and sorting. I'll keep searching with this one.


Bug 8:

https://i.imgur.com/7kJG5CK.jpg

Wallet passwords can't be removed. Attempting to remove the encryption leaves the wallet encrypted, and errors in the log.

Code:

(ERROR) ArmoryUtils.py:2786 - Error in pybkgdthread: No passphrase/key provided to unlock wallet!
Traceback (most recent call last):
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ArmoryUtils.py", line 2784, in run
    self.output = self.func()
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/armoryengine/ArmoryUtils.py", line 2721, in funcPartial
    return thefunc(*args, **kwargs)
  File "/Applications/Armory.app/Contents/MacOS/py/usr/lib/armory/qtdialogs.py", line 13214, in exec_async
    raise e
PassphraseError: No passphrase/key provided to unlock wallet!

Bug 9:

Crash while low on memory but scanning the blockchain. Should be using swap, but seems to have decided not to.

Code:

Python(39931,0x107904000) malloc: *** mach_vm_map(size=18446744073709490176) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
libc++abi.dylib: terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
/Applications/Armory.app/Contents/MacOS/Armory: line 23: 39931 Abort trap: 6           $DIRNAME/Python $ARMORYDIR/ArmoryQt.py

Bug 10:


https://i.imgur.com/mGuCSqX.jpg

The "No Wallet Error Found" looks like a "no wallet found" error not a "consistency check passed" sort of thing. It made me jump the first time I saw it, expecting to have had all of my wallets deleted. I don't think I'm alone in finding that one confusing.

In the latest RC it just reads "Wallet Consistency Check" and no further information given which is even more confusing.


Style more than bug:

https://i.imgur.com/OegZanN.jpg

Much less of an issue, but the two labels aren't opposites. "Encrypted" and "not encrypted" would make more sense, it's always struck me as a bit strange whenever I see it.

[etotheipi]

Last one, I think!  


  Armory 0.91.1-rc3 for Windows XP, Vista, 7, 8+ 32- and 64-bit
  Armory 0.91.1-rc3 for Ubuntu 12.04+ 32bit
  Armory 0.91.1-rc3 for Ubuntu 12.04+ 64bit
  Armory 0.91.1-rc3 for Raspbian armhf
  Armory 0.91.1-rc3 for MacOSX 10.7+ 64bit


  Armory 0.91.1-rc3 Offline Bundle for Ubuntu 12.04 32bit
  Armory 0.91.1-rc3 Offline Bundle for Ubuntu 12.04 64bit
  Armory 0.91.1-rc3 Offline Bundle for Raspbian (armhf)

  Armory 0.91.1-rc3:  Signed hashes of all installers

Note I switched around the versioning, and the update system doesn't handle it anymore.  I'm now doing 0.91.1-rcX instead of 0.91.0.99 that I was doing before.  The update system only notifies when a higher version number is available, but these all appear to be the same version number.  So you can get the testing release from the secure downloader, you just won't be notified of it (even then, you'd have to have enabled it in your settings to get notified of testing releases).

[etotheipi]

P.S. - The RPi offline bundle was created automatically as part of my new set of release scripts, but I haven't really tested it.  Don't expect it to work!  But it will later today or tomorrow when I do a final release.  The regular RPi package works, though.

[drips]

Last one, I think!

None of my bugs are fixed in that as far as I can see. I re-tested removing encryption, finding the address book on Windows. Don't have time to retest the rest, but those are both sort of important for a full release and are present in rc3.

[etotheipi]

Last one, I think!

None of my bugs are fixed in that as far as I can see. I re-tested removing encryption, finding the address book on Windows. Don't have time to retest the rest, but those are both sort of important for a full release and are present in rc3.

My apologies, I actually somehow didn't get notified of your post until I noticed while posting RC3.

Some of them are more complex to fix than others.  Even after reviewing them, I have determined that they are worth fixing, but not stirring up things for this release.  As such, you will get your appropriate bounties, but it the actual fixes will go into the next version. 

The exceptions are Bug 3 which should've been fixed, and Bug #8 that we will look at before the final release.  Otherwise, I suspect all these bugs were in the 0.91 release as well, which this release is going to replace.  It's not that they shouldn't be fixed -- we appreciate the feedback and will fix them -- it's that I need to make sure I didn't break stuff in 0.91.1 that worked in 0.91.  All the other stuff can go int 0.91.2 or 0.92.

In general, we need some help with widgets, layouts, etc.  A few of your reports are more systemic issues with the way we use Qt that allows windows to be spawned smaller than necessary to show everything, or spawning them off the screen.  We'll get to those eventually.  P.S.  What is your screen resolution?

[drips]

Last one, I think!

None of my bugs are fixed in that as far as I can see. I re-tested removing encryption, finding the address book on Windows. Don't have time to retest the rest, but those are both sort of important for a full release and are present in rc3.

My apologies, I actually somehow didn't get notified of your post until I noticed while posting RC3.

That's fine.

A few of your reports are more systemic issues with the way we use Qt that allows windows to be spawned smaller than necessary to show everything, or spawning them off the screen.  We'll get to those eventually.  P.S.  What is your screen resolution?

Where the OSX screenshots were taken is a 1440x900px MacBook, the XP screenshots were I think taken on the same. I'll make note of that next time, I had forgotten that QT would be using relative/absolute/etc positioning when spawning them. Bitcoin-QT had similar issues for a while, so I understand it's less than optimal for working with.

[etotheipi]

....I had forgotten that QT would be using relative/absolute/etc positioning when spawning them. Bitcoin-QT had similar issues for a while, so I understand it's less than optimal for working with.

At a more technical level, most of our dialogs are spawned as a subclass of QDialog.  And I think our subclass is not doing the placement correctly.  But that means we can fix all of them at once, but I also don't want to risk messing with it for this release.  The next one...

The squished'ness might be similar -- we gotta find the right method to tell Qt that to give each of those widgets and absolute minimum size, without having to set them explicitly each time.  We'll see what we can do in 0.91.2.

[Corelianer]

The Root-Key ist still overlapped by the border in the printout and the preview.

[etotheipi]

The Root-Key ist still overlapped by the border in the printout and the preview.

We've tried to fix this and even when we think we fixed it or breaks for someone else.  This is why we added the warnings to verify the number of columns, and posters you if you don't test the backup.  We're thinking of even REQUIRING the backup test.

[etotheipi]

Sorry for the delay everyone.  Finally found a spare minutes to go through this thread and collect the list of bounties.  Here's what I got:

qnxt      -      3 x 0.01 + 2 x 0.03
george51  -      1 x 0.01
brangdon  -      4 x 0.01
escrow.ms -      1 x 0.01
ncs0ne     -     1 x 0.01
TheAwer   -      1 x 0.01
jl2012    -      2 x 0.01
Corelianer-                2 x 0.03
KaChingCoinDev -           1 x 0.03
drips          -           4.5 x 0.03

Keep in mind I'm only providing bounties for first-reported instances of bugs.  There were a lot of repeats in there.  In one case, I think I gave someone a bounty for a repeated bug, but only because we claimed to have fixed it and it wasn't fixed.  

Please PM me with your payout address, and a statement about whether you're okay to receive it as part of a single all-bounty-payout transaction.  I will honor requests for separate transactions, if necessary.

[qnxt]

Noticed a couple still aren't fixed, even though supposedly in the queue...neither of these are a big deal, just want to make sure they didn't get forgotten since one is a trivial fix.

From your list here https://bitcointalk.org/index.php?topic=550804.msg6005108#msg6005108, still broken in Armory 0.91.2 on OS X 10.9.2:
Auto-detect OS in secure downloader
Update "About" window with proper copyright years

(Edit: To clarify, the bounties are fine. Just want to make sure you didn't forget those bugs.)

[etotheipi]

So far I'm still missing bounty addresses from a few people:
   george51
   brangdon
   ncs0ne
   TheAwer

Since you guys have been quite patient, I'll just send out what I've got so far.   I'll send out the rest when/if they send me their addresses!

@qnxt

I did fix the copyright year on our development branch.  The "secure downloader" auto-detect was more than a simple fix, so I also deferred that to the next version.  In fact, I'm going to totally rework that dialog, because I really don't like the way it organizes the downloads.  I think I'll make the version number selectable and then show all available downloads for that version.  Then this bug doesn't really mean much...

Regardless, thanks for pushing it.  Anyone else, if you think I overlooked something you found, let me know!  Sending out 6 of the 10 bounty payments in a few minutes.

[george51]

So far I'm still missing bounty addresses from a few people:
   george51
   brangdon
   ncs0ne
   TheAwer

Since you guys have been quite patient, I'll just send out what I've got so far.   I'll send out the rest when/if they send me their addresses!

@qnxt

I did fix the copyright year on our development branch.  The "secure downloader" auto-detect was more than a simple fix, so I also deferred that to the next version.  In fact, I'm going to totally rework that dialog, because I really don't like the way it organizes the downloads.  I think I'll make the version number selectable and then show all available downloads for that version.  Then this bug doesn't really mean much...

Regardless, thanks for pushing it.  Anyone else, if you think I overlooked something you found, let me know!  Sending out 6 of the 10 bounty payments in a few minutes.

Apologies it is late - just sent the address in a PM

Cheers

[PodBayDoors]

Is there a pointer to the latest version? My version (v 0.91.99.2) does a 99% crash after Building database. Win 7 64-bit 4 gigs of RAM (not enough)