Bitcoin Core (Bitcoin-Qt) 0.9.1 released - update required

[merockstar]

Is there a quick guide to install this ?

I have just switched from windows to Ubuntu, Help!

I got 0.9.0 installed via PPA but the PPA is not updated yet ( + I would like to know how to do it without)

I have :-

Downloaded bitcoin-0.9.1-linux.tar.gz

Then tar xvzf bitcoin-0.9.1-linux.tar.gz


This gives me a folder with bin + src but no ./configure. src has but that  fails.

Obviously I just don't get it  

cd bin - change directory to the bin folder you just unzipped
cd 64 (or 32 depending on your processor) - change directory again to one of two directories inside /bitcoin-blahblahblah/bin/
./bitcoin-qt - execute the binary file

you don't need anything in the src directory, because you want to run a pre-compiled binary (kind of the linux equivalent to a windows .exe file). everything in the src directory is for that.

http://www.devtome.com/doku.php?id=making_a_qt_wallet_work_in_ubuntu_12.04

[merockstar]

Rawted,

Have you tried running bitcoin-qt with -rescan flag?

right click on bitcoin icon. go to properties, and where it says C:\Windows\Program Files(x86)\Bitcoin\bitcoin-blahblahblah.exe (or whatever yours says) add -rescan, run it, and let the blockchain resync.

then go back and remove the flag because you wont want to resync after everytime you run the client.

[southerngentuk]

cd bin - change directory to the bin folder you just unzipped
cd 64 (or 32 depending on your processor) - change directory again to one of two directories inside /bitcoin-blahblahblah/bin/
./bitcoin-qt - execute the binary file

you don't need anything in the src directory, because you want to run a pre-compiled binary (kind of the linux equivalent to a windows .exe file). everything in the src directory is for that.

http://www.devtome.com/doku.php?id=making_a_qt_wallet_work_in_ubuntu_12.04

Thanks, I had resolved the issue by moving bitcoin-qt to the correct directory however this was really helpful in my understanding. 

[Geremia]

Why isn't 0.9.1 on SourceForge, and what is its checksum?

You should be verifying the PGP sigs from https://github.com/bitcoin/gitian.sigs

thanks

[Dabs]

Well, one good side effect of this release is that a lot of people will upgrade. Which means more nodes to relay my 0.00001 transaction fee transaction.

[Corelianer]

I'm not very happy about the information system. A notification integration that there is a new version available would be the least in the Bitcoin Core.
I wouldn't force the users to upgrade their Bitcoin Core, but at least an Integrated Info-System would be highly apreciated.

That I have to go to the Bitcointalk Forum to read about it, is terrible in my eyes.

[bananahunter67]

Thanks for info. Is electrum compromised as well?

[Luke-Jr]

I'm not very happy about the information system. A notification integration that there is a new version available would be the least in the Bitcoin Core.
I wouldn't force the users to upgrade their Bitcoin Core, but at least an Integrated Info-System would be highly apreciated.

That I have to go to the Bitcointalk Forum to read about it, is terrible in my eyes.

It exists. It just wasn't used for 0.9.1.

[Vyker]

Does anyone know if this affects Armory wallets? if so, how do we upgrade safely?

[7Priest7]

Does anyone know if this affects Armory wallets? if so, how do we upgrade safely?

Probably, Armory uses the bitcoin daemon.
Just upgrade the bitcoin daemon(packaged with bitcoin-qt/core.)

In reality, I've not seen any evidence to prove this vulnerability could effect a average end bitcoin user behind a router.

EDIT:
Modern routers do more than route network traffic.
They block incoming connections.
My understanding of the heartbleed venerability leads me to believe it would require a open port to request the memory dumps.

I felt I should probably elaborate on my above statement.

[PrintMule]

New like these make me wonder if people should avoid new updates if they are not critical. Like an update to 0.9.0 - I did not read changelog and thought, why bother updating...

[wumpus]

New like these make me wonder if people should avoid new updates if they are not critical. Like an update to 0.9.0 - I did not read changelog and thought, why bother updating...

It's perfectly reasonable to wait a while after a release, and not jump on every update. This is the reason that automatic updates aren't implemented.

[huggybear]

Can someone tell me why the bitcoin-qt file isn't executable in linux?

[coinflow]

New like these make me wonder if people should avoid new updates if they are not critical. Like an update to 0.9.0 - I did not read changelog and thought, why bother updating...

It's perfectly reasonable to wait a while after a release, and not jump on every update. This is the reason that automatic updates aren't implemented.

That makes only sense, if it is no hardfork. Otherwise you'd be on the wrong fork, missing coins that were send to you from the new fork and vice versa.

[Rawted]

Still missing those coins. It really is quite perplexing. The dates of the transactions with those coins are all from the june/july 2013 range and up until 0.9.1 were valid confirmed coins, and are now conflicted transactions and missing coins. Does this mean I was passed bad transactions previously and it's only now showing up? If so, how were those coins spendable prior?

[/dev/null]

Still missing those coins. It really is quite perplexing. The dates of the transactions with those coins are all from the june/july 2013 range and up until 0.9.1 were valid confirmed coins, and are now conflicted transactions and missing coins. Does this mean I was passed bad transactions previously and it's only now showing up? If so, how were those coins spendable prior?

Do one thing, import wallet on blockchain.info then make a new wallet and send coins to your qt wallet. (Make sure to send a test amount first)

[Comrade Capitalist]

Can someone tell me why the bitcoin-qt file isn't executable in linux?

I use a very simple workaround. I created a shortcut on the desktop and pointed it to the bitcoin-qt file. That's it.

[huggybear]

Can someone tell me why the bitcoin-qt file isn't executable in linux?

I use a very simple workaround. I created a shortcut on the desktop and pointed it to the bitcoin-qt file. That's it.

Sorry it's all Greek to me I only use Linux for Bitcoin-QT. Can you explain me step by step how I can bitcoin-qt get running. At version 0.8.6. the bitcoin-qt file was executable but in the new version it is a shared libary. I opened the context menu and tried to open the file with "run application" but nothing happens.

[MysteryMiner]

This is extra bad OpenSSL bug. With Certificate Patrol extension installed on Firefox I see almost every site changing SSL keys. Already changed all my important passwords on websites.

But Bitcoin is not that badly affected. Deep web are changing .onion addresses, people changing TorChat identities. It is chaos there right now and recent attack on Hidden Wiki by some Anonymous moron does not help.

Maybe The Hidden Wiki got it's legendary .onion key leaked because of this OpenSSL vulnerability? This key leaking is exactly what the vulnerability will allow to do. Previously I thought that the hidden wiki's VPS host was broken by password reset.

[Comrade Capitalist]

Can someone tell me why the bitcoin-qt file isn't executable in linux?

I use a very simple workaround. I created a shortcut on the desktop and pointed it to the bitcoin-qt file. That's it.

Sorry it's all Greek to me I only use Linux for Bitcoin-QT. Can you explain me step by step how I can bitcoin-qt get running. At version 0.8.6. the bitcoin-qt file was executable but in the new version it is a shared libary. I opened the context menu and tried to open the file with "run application" but nothing happens.

1. Use instructions from this link: http://xmodulo.com/2013/11/create-desktop-shortcut-launcher-linux.html (or google linux+desktop+shortcut)
2. In the “command” field put the correct path to your “bitcoin-qt” file, i.e. “/home/user/bitcoin-0.9.1-linux/bin/64/bitcoin-qt” (without quotes) for example.
3. Uncheck “run in terminal” and check “is executable”, if those checkboxes exist.
4. Use new shortcut (or launcher).