Bitcoin Forum
May 04, 2024, 09:40:43 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Please help test: versions 0.5.3rc3 and 0.4.4rc3  (Read 1883 times)
Luke-Jr (OP)
Legendary
*
expert
Offline Offline

Activity: 2576
Merit: 1186



View Profile
March 07, 2012, 11:50:02 PM
 #1

Bitcoin version 0.4.4rc3 and 0.5.3rc3 are now available for download.

These are bugfix-only releases based on 0.4.0 and 0.5.1, respectively.

Please report bugs by replying to this forum thread.

Stable source code is hosted at Gitorious:
  http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.4.4rc3#.tar.gz
  http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.3rc3#.tar.gz

Windows binaries are on my site:
  http://luke.dashjr.org/programs/bitcoin/files/bitcoind-0.4.4/test/
  http://luke.dashjr.org/programs/bitcoin/files/bitcoind-0.5.3/test/

BUG FIXES

Since 0.4.3 and 0.5.2:
  • Various compile warning fixes.
  • Updated fallback seed nodes, chosen based on uptime and version.
  • February 15, 2012 testnet difficulty calculation changes.
  • Reannounce UPnP port forwarding rules every 20 minutes, to work around routers that expire them.
  • Verify integrity of private keys in wallet file at startup.
  • Don't store completely invalid transactions in memory.
  • Recommend a secure password for bitcoind, when none is set, and increase JSON-RPC delay when a wrong password is attempted.
  • Fix incorrect memory release, which may have caused crashes.
  • Use UPnP IP in version messages when available, and never send non-routable IPs.
  • Do not attempt to create "CAddress" objects for invalid accepts.
  • Several shutdown-related fixes.
  • Various wallet locking fixes.
  • Fixed memory leaks.
  • Fixed a wrong error message when failing to get external IP from webservice.
  • New checkpoint at block 168,000.
  • A fix for a potential DoS attack.
  • BIP 30: Forbid overwriting unspent transactions with duplicates.
Just since 0.5.2:
  • Make transaction description read-only.
  • Add "About Qt" menu option to show built-in Qt About dialog.
  • Add missing "Clear all" tooltip.
  • Fix building test framework with shared boost libraries.
  • Revert to global blockchain download progress indication.
  • Minor translation/capitalization fixes.
  • Restructure credit transaction decomposition to fix issue #689.
  • Enable accessible widgets Qt module on win32, so that people with screen readers such as NVDA can make sense of it.
  • Prevent window from being shown momentarily when using -min
  • Fix Minimize to the tray instead of the taskbar.
  • Fix parsing of invalid bitcoin URIs (with bitcoin:// instead of simply bitcoin:)
  • Don't overwrite user-entered labels with ones from the address book.
  • Display a message box with help on Windows for --help
  • Don't show splash screen when -min is specified on the command line.
  • Don't show weird tooltip when last received block has a future timestamp.



Thanks to everybody who contributed code or helped test these releases:

Pieter Wuille
Luke Dashjr
Wladimir J. van der Laan
Gavin Andresen
Matt Corallo
Lars Rasmusson
Janne Pulkkinen
Gregory Maxwell
Daniel Folkinshteyn
Chris Moore

"Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714815643
Hero Member
*
Offline Offline

Posts: 1714815643

View Profile Personal Message (Offline)

Ignore
1714815643
Reply with quote  #2

1714815643
Report to moderator
1714815643
Hero Member
*
Offline Offline

Posts: 1714815643

View Profile Personal Message (Offline)

Ignore
1714815643
Reply with quote  #2

1714815643
Report to moderator
1714815643
Hero Member
*
Offline Offline

Posts: 1714815643

View Profile Personal Message (Offline)

Ignore
1714815643
Reply with quote  #2

1714815643
Report to moderator
grue
Legendary
*
Offline Offline

Activity: 2058
Merit: 1431



View Profile
March 08, 2012, 01:28:17 AM
 #2

I'm getting

Error loading wallet.dat: Wallet corrupted     

It is pitch black. You are likely to be eaten by a grue.

Adblock for annoying signature ads | Enhanced Merit UI
Luke-Jr (OP)
Legendary
*
expert
Offline Offline

Activity: 2576
Merit: 1186



View Profile
March 08, 2012, 02:03:36 AM
 #3

I'm getting

Error loading wallet.dat: Wallet corrupted
Even after restoring your backup? Can you join #bitcoin-dev to troubleshoot?

grue
Legendary
*
Offline Offline

Activity: 2058
Merit: 1431



View Profile
March 08, 2012, 03:32:01 AM
 #4

I'm getting

Error loading wallet.dat: Wallet corrupted
Even after restoring your backup? Can you join #bitcoin-dev to troubleshoot?
No, i was using 0.4.2 before, and it worked fine. When i changed to 0.4.4, i got that error, and when i restored the old executable, it was working fine again. Seems like an incompatible wallet version to me.

It is pitch black. You are likely to be eaten by a grue.

Adblock for annoying signature ads | Enhanced Merit UI
Luke-Jr (OP)
Legendary
*
expert
Offline Offline

Activity: 2576
Merit: 1186



View Profile
March 08, 2012, 03:35:32 AM
 #5

I'm getting

Error loading wallet.dat: Wallet corrupted
Even after restoring your backup? Can you join #bitcoin-dev to troubleshoot?
No, i was using 0.4.2 before, and it worked fine. When i changed to 0.4.4, i got that error, and when i restored the old executable, it was working fine again. Seems like an incompatible wallet version to me.
My best guess, at this point, is that your wallet has a corrupt private key which was not properly detected in older versions. Could you check debug.log?

Pieter Wuille
Legendary
*
qt
Offline Offline

Activity: 1072
Merit: 1174


View Profile WWW
March 08, 2012, 03:39:16 AM
 #6

No, i was using 0.4.2 before, and it worked fine. When i changed to 0.4.4, i got that error, and when i restored the old executable, it was working fine again. Seems like an incompatible wallet version to me.

You did not ever use 0.6.0rc1? (I ask because that had a known and fixed bug that can cause this)

I do Bitcoin stuff.
grue
Legendary
*
Offline Offline

Activity: 2058
Merit: 1431



View Profile
March 08, 2012, 03:41:06 AM
 #7

My best guess, at this point, is that your wallet has a corrupt private key which was not properly detected in older versions. Could you check debug.log?
I copied 0.4.4 back, and now I'm getting a slightly different error.

debug.log
Code:
Bitcoin version 0.4.4-beta
OS version Windows 7 (build 7601, Service Pack 1), 64-bit edition
System default language is 60 English_United States.1252
Language file locale/en_US/LC_MESSAGES/bitcoin.mo (English (U.S.))
Default data directory C:\Users\Administrator\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open strLogDir=C:\Users\Administrator\AppData\Roaming\Bitcoin/database strErrorFile=C:\Users\Administrator\AppData\Roaming\Bitcoin/db.log
Loaded 69349 addresses
 addresses              7809ms
Loading block index...


************************
EXCEPTION: 11DbException      
Db::open: Invalid argument      
C:\Users\Administrator\Desktop\bitcoin\bitcoin.exe in AppInit()      



************************
EXCEPTION: 11DbException      
Db::open: Invalid argument      
C:\Users\Administrator\Desktop\bitcoin\bitcoin.exe in CMyApp::OnUnhandledException()      

db.log
Code:
file unknown has LSN 8/3751694, past end of log at 1/327
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
__db_meta_setup: C:\Users\Administrator\AppData\Roaming\Bitcoin\blkindex.dat: unexpected file type or format

It is pitch black. You are likely to be eaten by a grue.

Adblock for annoying signature ads | Enhanced Merit UI
Luke-Jr (OP)
Legendary
*
expert
Offline Offline

Activity: 2576
Merit: 1186



View Profile
March 08, 2012, 03:50:59 PM
 #8

My best guess, at this point, is that your wallet has a corrupt private key which was not properly detected in older versions. Could you check debug.log?
I copied 0.4.4 back, and now I'm getting a slightly different error.
Does 0.4.2 still work? This looks like blkindex.dat got corrupted somehow.

grue
Legendary
*
Offline Offline

Activity: 2058
Merit: 1431



View Profile
March 08, 2012, 06:15:55 PM
 #9

My best guess, at this point, is that your wallet has a corrupt private key which was not properly detected in older versions. Could you check debug.log?
I copied 0.4.4 back, and now I'm getting a slightly different error.
Does 0.4.2 still work? This looks like blkindex.dat got corrupted somehow.
Nope, 0.4.2 doesn't work either now. Although i got it to work by deleting everything except for wallet.dat. 0.4.4 still doesn't work though.

It is pitch black. You are likely to be eaten by a grue.

Adblock for annoying signature ads | Enhanced Merit UI
bitcoinsarefun
Member
**
Offline Offline

Activity: 98
Merit: 10



View Profile
March 09, 2012, 05:09:24 PM
 #10

I've got the 5.3 win32 release installed in a vm, is there anything in particular that needs testing?
Luke-Jr (OP)
Legendary
*
expert
Offline Offline

Activity: 2576
Merit: 1186



View Profile
March 10, 2012, 07:48:00 PM
 #11

My best guess, at this point, is that your wallet has a corrupt private key which was not properly detected in older versions. Could you check debug.log?
I copied 0.4.4 back, and now I'm getting a slightly different error.
Does 0.4.2 still work? This looks like blkindex.dat got corrupted somehow.
Nope, 0.4.2 doesn't work either now. Although i got it to work by deleting everything except for wallet.dat. 0.4.4 still doesn't work though.
Can we get debug.log with the original issue (ie, when 0.4.2 works)?

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!