Bitcoin Forum
May 22, 2024, 04:19:47 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: [ANN] Armory Multi-Sig with Simulfunding [BOUNTY 0.03 per bug] on: July 22, 2014, 06:09:33 PM
Bug 1:

Replicate:
  • make a new transaction, up until the Confirm Transaction screen
  • close the confirm screen

Wallet is now completely non-responsive to all button clicks, must be force quit due to the close buttons not working.


Bug 2:

If all internet connectivity is disabled in the settings, outgoing connections are still made regardless.






Bug 3:



Replicate:
  • make a transaction
  • tick "use existing change address"

Text is squashed, if the window is made bigger the radio buttons don't work properly.

2  Bitcoin / Development & Technical Discussion / Re: [BOUNTY 0.03/bug] Help test next major release of Armory! (0.91.1) on: April 30, 2014, 05:31:20 PM
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.
3  Bitcoin / Development & Technical Discussion / Re: [BOUNTY 0.03/bug] Help test next major release of Armory! (0.91.1) on: April 30, 2014, 05:14:00 PM
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.
4  Bitcoin / Development & Technical Discussion / Re: [BOUNTY 0.03/bug] Help test next major release of Armory! (0.91.1) on: April 29, 2014, 02:30:22 PM
Bug 1:

Fixed in rc2, missed that further down the topic.



Bug 2:



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:



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:



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:






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:



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:



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:




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:



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.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!