Quote from: Kazu on September 01, 2013, 08:46:51 PM

Quote from: jackjack on September 01, 2013, 08:06:54 PM

Quote from: Kazu on September 01, 2013, 07:53:22 PM

Bitcoin isn't running. I have full 777 permissions in that directory. If I rename wallet.dat to otherwallet.dat, and then run Bitcoin (to generate new wallet.dat file), then stop Bitcoin, then execute the exact same command, then it will work. Does this indicate a corrupted wallet.dat file?

Likely, try the wallet recovery feature on this corrupted file

would it also be possible that the file isn't matching something else contained in my Bitcoin data directory? I noticed that your program is reading the DB files and you should probably know that the wallet.dat file is not my own, its someone else's that I just plopped down into my data directory.

What DB files are you talking about? It should only read wallet.dat

Quote from: Kazu on September 01, 2013, 08:46:51 PM

Quote

Quote from: Kazu on September 01, 2013, 07:53:22 PM

Also, you may want to tell the user something before changing his wallet selection. When I went pywallet.py --walletdump --wallet=otherwallet.dat (the file I then renamed to wallet.dat) it just walletdumped wallet.dat because it couldn't read otherwallet.dat or something. That managed to confuse me a bit.

This is REALLY odd
This is not an expected behavior, nor something I ever heard...
Are you sure this is what is happening?
No symlinks?

I have no idea. There is a symlink, so I didn't have to put in the datadir param. But if I do the same thing setting datadir to go "around" the symlink, same thing is happening.

Ok... I don't see what can happen here
Would you mind sending me the corrupt wallet.dat (it's encrypted, right?) so that I can see what I can do on my side?