Bitcoin Forum

Bitcoin version 0.7.1 is now available from:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.1/

This is a bug-fix minor release.

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues

Project source code is hosted at github; you can get
source-only tarballs/zipballs directly from there:
  https://github.com/bitcoin/bitcoin/tarball/v0.7.1  # .tar.gz
  https://github.com/bitcoin/bitcoin/zipball/v0.7.1  # .zip

Ubuntu Linux users can use the "Personal Package Archive" (PPA)
maintained by Matt Corallo to automatically keep
up-to-date.  Just type:
  sudo apt-add-repository ppa:bitcoin/bitcoin
  sudo apt-get update
in your terminal, then install the bitcoin-qt package:
  sudo apt-get install bitcoin-qt

KNOWN ISSUES
------------

Mac OSX 10.5 is no longer supported.

How to Upgrade
--------------

If you are running an older version, shut it down. Wait
until it has completely shut down (which might take a few minutes for older
versions), then run the installer (on Windows) or just copy over
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

If you were running on Linux with a version that might have been compiled
with a different version of Berkeley DB (for example, if you were using an
Ubuntu PPA version), then run the old version again with the -detachdb
argument and shut it down; if you do not, then the new version will not
be able to read the database files and will exit with an error.

Explanation of -detachdb (and the new "stop true" RPC command):
The Berkeley DB database library stores data in both ".dat" and
"log" files, so the database is always in a consistent state,
even in case of power failure or other sudden shutdown. The
format of the ".dat" files is portable between different
versions of Berkeley DB, but the "log" files are not-- even minor
version differences may have incompatible "log" files. The
-detachdb option moves any pending changes from the "log" files
to the "blkindex.dat" file for maximum compatibility, but makes
shutdown much slower. Note that the "wallet.dat" file is always
detached, and versions prior to 0.6.0 detached all databases
at shutdown.

New features
------------

* Added a boolean argument to the RPC 'stop' command, if true sets
  -detachdb to create standalone database .dat files before shutting down.

* -salvagewallet command-line option, which moves any existing wallet.dat
  to wallet.{timestamp}.dat and then attempts to salvage public/private
  keys and master encryption keys (if the wallet is encrypted) into
  a new wallet.dat. This should only be used if your wallet becomes
  corrupted, and is not intended to replace regular wallet backups.

* Import $DataDir/bootstrap.dat automatically, if it exists.

Dependency changes
------------------

* Qt 4.8.2 for Windows builds

* openssl 1.0.1c

Bug fixes
---------

* Clicking on a bitcoin: URI on Windows should now launch Bitcoin-Qt properly.

* When running -testnet, use RPC port 18332 by default.

* Better detection and handling of corrupt wallet.dat and blkindex.dat files.
  Previous versions would crash with a DB_RUNRECOVERY exception, this
  version detects most problems and tells you how to recover if it
  cannot recover itself.

* Fixed an uninitialized variable bug that could cause transactions to
  be reported out of order.

* Fixed a bug that could cause occasional crashes on exit.

* Warn the user that they need to create fresh wallet backups after they
  encrypt their wallet.

----------------------------------------------------
Thanks to everybody who contributed to this release:

Gavin Andresen
Jeff Garzik
Luke Dashjr
Mark Friedenbach
Matt Corallo
Philip Kaufmann
Pieter Wuille
Rune K. Svendsen
Virgil Dupras
Wladimir J. van der Laan
fanquake
kjj2
xanatos

For people bringing up new 0.7.1 nodes, here is an unofficial torrent of bootstrap.dat:

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

(if you already have the blockchain, bootstrap.dat is of no use to you; see link)

Seems like the PPA version has failed to build:
https://launchpadlibrarian.net/120177982/buildlog_ubuntu-quantal-amd64.bitcoin_0.7.0-quantal1_FAILEDTOBUILD.txt.gz
https://launchpad.net/~bitcoin/+archive/bitcoin/+build/3915177

For RPM user check here: http://www.openmamba.org/distribution/distromatic.html?tag=devel-contrib&pkg=bitcoin.i586 (http://www.openmamba.org/distribution/distromatic.html?tag=devel-contrib&pkg=bitcoin.i586)

When building bitcoind 0.7.0 from the Gentoo bitcoin overlay, there was a patchfile (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/eligius/sendfee/0.7.0-eligius_sendfee.patch.xz) applied if the eligius USE flag was set.  This appears not to have been updated for 0.7.1.  Is this something to be concerned about?  What changes does this patch make?  I'm not mining at Eligius...currently using Eclipse, but am considering shifting back to P2Pool.

(In the meantime, I've copied the 0.7.0 ebuild to a local overlay, commented out the Eligius patch code, and gotten 0.7.1 working on Gentoo.)

Thank you developers!

PS. The ubuntu ppa maintained by Matt Corallo is not updated yet  :(

 Thanks to the dev team !


The release of this feature together with jgarzick blockchain torrent initiative is a momentous event (a little more than a "minor" release imho)

The real change was adding -loadblock in 0.7.0. The only change in 0.7.1, is applying it automatically to any file called bootstrap.dat.

Using the donation link on TBF's website does not yield expected behavior. There is no error message indicating that bitcoin is already running, but no apparent action is taken by the running client.

Installed and running/catching up on blockchain on Win7 64.
Thanks folks.

Any way to have the client say "Hey update me theres a new one!"

I'm always missing out on the new updates :(

Moved to main branch of distro. Now the package is here: http://www.openmamba.org/distribution/distromatic.html?tag=devel&pkg=bitcoin.i586
Every time it'll be updated and accepted in main branch the package will be put there

In addition, clicking on the link multiple times creates multiple instances of the bitcoin process, but the user cannot see any affects of them starting. I didn't notice until I checked process explorer and noticed them running. Also, when the client is not running, clicking the link creates a process but no gui appears at all, neither the window nor the tray icon.

This is the command line of the spawned process:

thank you

Did you use the installer for upgrading 0.7.1? What OS are you using?
Can you please start regedit.exe and post what is listed as (default) in HKEY_CLASSES_ROOT\bitcoin\shell\open\command.

Did you give the client time to start-up before hammering that link over and over?

Thanks,
Dia

Yes. Win7x64.

I tried it with both the program running and with the program not running. In both instances, the link spawned new processes that appeared to do nothing.

Now that I check, the bitcoin program does not start up properly now. I cannot get a responsive gui.

You can try deleting the contents of "C:\ProgramData\boost_interprocess" when the client is shutdown and report back.

Dia

I am experiencing some problems after upgrading from 0.6.3 to 0.7.1 on the bitcoind that I use to process pyramining deposits and payouts. It is running on Linux (OpenSuSE 11.2).

My upgrade procedure:
- stopped 0.6.3 bitcoind
- replaced binaries with 0.7.1 ones
- started 0.7.1 bitcoind

At first, I had to download again all the blockchain because for some reason it was displaying the message "WARNING: Displayed transactions may not be correct!  You may need to upgrade, or other nodes may need to upgrade.", and I didn't find out how to repair it.

After the blockchain has been downloaded, it started working as expected, but after about 20 hours, I found it hung up and unresponsive. No way to stop it or kill it, even with -9.

After a reboot it started and worked well for a couple of hours, then the same trouble appeared again.

Environment:
ATOM D2500 dual core (64bit arch), 4GB/ram, 60Gb SSD, 100mbit/s ip connectivity, OpenSuSE Linux 12.1.
wallet.dat is around 200MB in size.

Behaviour: after working normally for few hours, it freezes. Debug log displays RPC commands, but they never return any result.

I am currently downgrading to 0.6.3, I will keep an eye open to see if the issue disappears using this version.

Doing this did not improve the situation.

However, after a restart, the gui appears and is responsive. Also, the donation link works. I think you should add a reboot step in the upgrade instructions. Thanks for your help, and for another release!

@LightRider
I need to understand, when did you reboot and realized that helped? Seems a little weird to me. Perhaps there were orphan instances running, which went away after the reboot.

Dia

Strange: I use 0.7.1 on 2 different PC with no issues (I've upgraded them from 0.6.3 to 0.7 and then 0.7.1). Do you've compiled yourself the program or you're using the precompiled version?
Give a try at the RPM version or try to remove the blk* files in the bitcoin directory

On other machines it runs correctly, but they handle a lot less addresses/transactions, and yes, I tried to download the blockchain from scratch, but the issue appeared again.

Upgraded -> Started bitcoin -> Tried donation links which failed -> Quit bitcoin -> Found multiple donation link processes and force closed them -> Tried starting bitcoin again, but would get no gui or unresponsive gui -> Tried your suggestion and got same result -> Reboot machine -> bitcoin works fine

In the thread for 0.7.1rc1 I reported a bug, and the final 0.7.1 still has it:
   https://bitcointalk.org/index.php?topic=117874.msg1273313#msg1273313

Just wondering, if no one else can reproduce it, or if no one else of
you following these threads ever uses the "move" command.

I opened an issue for this:
https://github.com/bitcoin/bitcoin/issues/1960

You are free to do this everytime you observe issues :).

Dia

@Diapolo: thanks for forwarding it to a more appropriate place!

I admit, I felt like trying to avoid the umpty+1st registration to
yet another bugtracking system (already have a sourceforge login,
and a couple others, but haven't used git so far).

In case I find more bugs, I'll consider registering.

Can't update bitcoin-qt using the PPA on ubuntu 12.10 quantal.
I see on the browser it's supposed to be there, but the update doesn't find it, nor it comes listed on the Software center.

Sounds like your package info is outdated. Try opening up terminal and running
Then run
If that doesn't work, post the output of

Hi All

I am having problems with ubuntu 64 bit 12.10 and bitcoin-qt 0.7.1.. Both fresh install.. I get no gui?? Can see bitcoind running in system resources??  ???

Anyone else having the same prob??

Either run bitcoind, or bitcoin-qt. You can't run both at once (well, you can, but not out of the box, and it won't do what you want)

Thanks mate  :)!

Now, what happened next!

So I ran bitcoin-qt and turned off bitcoind.. It was syncing fine, until I tried to restart the program. Then I got:

A fatal error has occured. Bitcoin can no longer continue safely and will quit.

Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.

 ???

You *do* have a backup, don't you?  Terminate all running clients, restore from backup and restart...

Don't have one? And more than just a few peanuts of btc in the wallet? Probably not all hope is lost,
but prepare for a bumpy road ahead.

Bumpy road??

Why would my wallet be lost anyhow?

I did not say "lost".

From what you wrote, it seems that the bitcoin-client has
difficulties to open and use your wallet. Most likely the
information is still stored in it, but you may have to do
some sorcery to get the client use it.  The much easier
way, of course, is when you have a backup.

I'm not a developer of any bitcoin-client.

What's current state of affairs?  Do you have a backup?
What order of value was stored in it? (i.e.: does it even
pay to spend effort on recovering it?)

Ummm, in what way are your RPM's "The offical frontend for the bitcoin cryptocurrency" ??

And what guarantees, (sigs, etc) do you supply that you actually built these binaries from the "official" source?

I ask because you post this in the official announcement thread for latest version release.

As for every package there is no warranty except the trust in the packager, but the source RPM is there too, so everybody can check it and eventually rebuilt from scratch  to verify that is built from the official source.

The sentence "The official frontend for the bitcoin cryptocurrency" is in the description and refers to the program bitcoin  not to my package; the description is there to make the search of the package faster in our frontend, but if it's misleading I can remove the sentence.

No worries, had none in there anyway.

My main problem is every time I try to sync the blockchain I keep getting the same error before it completes.

Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.

I delete all files and restart the process and same thing happens again and again...

Thanks for any help..

So yes, I reinstalled it again and half hour into it I get the same msg again.
"WARNING: Displayed transactions may not be correct!  You may need to upgrade, or other nodes may need to upgrade."

Then when I close and restart the program, I get:
A fatal error has occured. Bitcoin can no longer continue safely and will quit.

Exception: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
bitcoin in Runaway exception.

Any ideas??

Can you pastebin your debug.log?

You can also try the newly introduced (0.7.1):

Dia

Here it is. I am running 0.7.1. I have cut the log a bit short.

Thanks

ERROR: FetchInputs() : 5b2febc48a mempool Tx prev not found a5d15e1498 stored orphan tx 5b2febc48a (mapsz 5613) received block 00000000000002e174e6 ProcessBlock: ORPHAN BLOCK, prev=00000000000007328218 ERROR: FetchInputs() : fafa937e40 mempool Tx prev not found 4578de4640 stored orphan tx fafa937e40 (mapsz 5614) Flushed 10661 addresses to peers.dat  246ms received block 00000000000002dd859a ProcessBlock: ORPHAN BLOCK, prev=00000000000002e174e6 Added 1 addresses from 94.179.214.34: 13 tried, 10648 new ERROR: FetchInputs() : 955e361a1a mempool Tx prev not found 6e08b7388c stored orphan tx 955e361a1a (mapsz 5615) ERROR: FetchInputs() : 1d5d5ac640 mempool Tx prev not found 52cd767862 stored orphan tx 1d5d5ac640 (mapsz 5616) ERROR: FetchInputs() : 7b2dcce78d mempool Tx prev not found 5b2febc48a stored orphan tx 7b2dcce78d (mapsz 5617) received block 00000000000002516ec0 ProcessBlock: ORPHAN BLOCK, prev=00000000000002dd859a ERROR: FetchInputs() : 23f9cd3e91 mempool Tx prev not found d281c0a3e2 stored orphan tx 23f9cd3e91 (mapsz 5618) ERROR: FetchInputs() : 6e9e03ae73 mempool Tx prev not found 5b2febc48a stored orphan tx 6e9e03ae73 (mapsz 5619) received block 0000000000000294a1bc ProcessBlock: ORPHAN BLOCK, prev=00000000000002516ec0 ERROR: FetchInputs() : 9666265669 mempool Tx prev not found fafa937e40 stored orphan tx 9666265669 (mapsz 5620) Added 1 addresses from 173.76.177.60: 13 tried, 10648 new ERROR: FetchInputs() : 5e07d9b38c mempool Tx prev not found 5b2febc48a stored orphan tx 5e07d9b38c (mapsz 5621) ERROR: FetchInputs() : 3f9a3d8ee2 mempool Tx prev not found 5b2febc48a stored orphan tx 3f9a3d8ee2 (mapsz 5622) ERROR: FetchInputs() : a993dd9d99 mempool Tx prev not found 4551f0e1cd stored orphan tx a993dd9d99 (mapsz 5623) ERROR: FetchInputs() : fd88eb3179 mempool Tx prev not found 5b2febc48a stored orphan tx fd88eb3179 (mapsz 5624) received block 000000000000066ecfe5 ProcessBlock: ORPHAN BLOCK, prev=0000000000000294a1bc Added 1 addresses from 173.76.177.60: 13 tried, 10649 new received block 000000000000010fa885 ProcessBlock: ORPHAN BLOCK, prev=000000000000066ecfe5 received block 00000000000004c689d9 ProcessBlock: ORPHAN BLOCK, prev=000000000000010fa885 ERROR: FetchInputs() : 879c40d7f5 mempool Tx prev not found 1d5d5ac640 stored orphan tx 879c40d7f5 (mapsz 5625) ERROR: FetchInputs() : 4a0138c922 mempool Tx prev not found e676005a6d stored orphan tx 4a0138c922 (mapsz 5626) received block 000000000000045c31bb ProcessBlock: ORPHAN BLOCK, prev=00000000000004c689d9 received block 000000000000051c24db ProcessBlock: ORPHAN BLOCK, prev=000000000000045c31bb received block 000000000000047ffa72 ProcessBlock: ORPHAN BLOCK, prev=000000000000051c24db ERROR: FetchInputs() : 6fc3777ee6 mempool Tx prev not found 2203f90fcb stored orphan tx 6fc3777ee6 (mapsz 5627) ERROR: FetchInputs() : a5c007a181 mempool Tx prev not found a993dd9d99 stored orphan tx a5c007a181 (mapsz 5628) received block 000000000000019b5080 ProcessBlock: ORPHAN BLOCK, prev=000000000000047ffa72 Flush(false) blkindex.dat refcount=0 ThreadSocketHandler exited ThreadMessageHandler exited ipcThread exited blkindex.dat checkpoint ThreadMapPort exited blkindex.dat closed wallet.dat refcount=0 wallet.dat checkpoint wallet.dat detach wallet.dat closed DBFlush(false) ended            1087ms StopNode() ThreadOpenConnections exited Flushed 10662 addresses to peers.dat  560ms Flush(true) DBFlush(true) ended               0ms Bitcoin exited Bitcoin version v0.7.1.0-geb49457-beta () Using OpenSSL version OpenSSL 1.0.1c 10 May 2012 Startup time: 30/10/12 18:59:17 Default data directory /home/yr/.bitcoin Used data directory /home/yr/.bitcoin dbenv.open LogDir=/home/yr/.bitcoin/database ErrorFile=/home/yr/.bitcoin/db.log Loading block index... LoadBlockIndex(): hashBestChain=0000000034bd1e0953a3  height=43788  date=04/03/10 20:29:39 Verifying last 2500 blocks at level 1  block index           18996ms Loading wallet... ************************ EXCEPTION: St13runtime_error       CDB() : can't open database file wallet.dat, error 12       bitcoin in Runaway exception       EnvShutdown exception: Invalid argument (22)

Did you try -salvagewallet (command-line option, which moves any existing wallet.dat
  to wallet.{timestamp}.dat and then attempts to salvage public/private
  keys and master encryption keys (if the wallet is encrypted) into
  a new wallet.dat. This should only be used if your wallet becomes
  corrupted, and is not intended to replace regular wallet backups.)?

Make a backup of your wallet.dat before anyway!

Dia

I get the same error Dia.. Any ideas?? Because Im running out of em ???

You could try older versions, perhaps one works, which would allow to transfer stored funds to a new wallet?
Sorry, I guess some of the core devs could perhaps give some more help here.

Dia

According to:


saving funds is not the issue.  It's just about that the program doesn't start at all
for him.

Yeah, no funds in there.. Just wanna wallet , goddamit  :D

If there are NO funds in, why not simply emty your data-dir and start from scratch?

Dia

I already tried that over 3-4 times.. Same keeps happening   :o

 ;D

I just cant figure this out ... YET ...  :P

As far as I know, it's supposed to be alarming. There were recently a lot of newbies complaining "Help! It's not working! I just bought coins and they're not showing up!! Where are they?! Oh, by the way, it hasn't finished synchronising yet, is that important?" *collective facepalming* Hopefully this way newbies will get the idea that they shouldn't even try to use the client until it is synchronised, and have some idea of what the problem might be if something goes wrong as a result.