Bitcoin Forum

Hello,

Since I made the latest update, every time I'm trying to start the Armory it says "Error Occured" "See the logfiles for details", and I just can open the damn client!

Here's the log it gives me:

Traceback (most recent call last):
  File "ArmoryQt.py", line 37, in <module>
  File "armoryengine.pyc", line 321, in <module>
  File "armoryengine.pyc", line 264, in findLatestBlkFiles
  File "armoryengine.pyc", line 122, in toPreferred
  File "armoryengine.pyc", line 116, in toUnicode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe9 in position 15: invalid continuation byte


The error being most probably

UnicodeDecodeError: 'utf8' codec can't decode byte 0xe9 in position 15: invalid continuation byte

I really don't know what to do, tried to downgrade it to see if it was a problem with the update itself, but it doesn't work. Bitcoin QT is opened, and everything is as it should. Does anyone know what to do??

Thank you!

Interesting, I thought I had solved that unicode issue in this release.  Can you please send me the full log file so I can see what's going on?  My screenname, @gmail.com

The underlying error that I thought I fixed was that your path to the Bitcoin homedirectory has lots of non-ASCII characters (what is on the English(US) key board).  I'm surprised the old one stopped working.  Have you changed your Bitcoin-Qt datadir recently? 

Armory never paid good attention to unicode issues before, and I finally made an effort in this last release.  Apparently I didn't quite get there...

Well this is the full log, I have cleared the txt document before opening Armory and these are the only lines I get, or maybe I'm doing something wrong but it's the only thing the log will show me. It will just loop these lines when I try to open it multiple times. I didn't change anything related to the path directory.

Does this compromise my wallets? I cannot get access to them.

Thanks for the quick reply.

Did you forget to send the log file? 

There's no compromise.  Armory bugs like this simply prevent you from using the program, but do not expose any private key (security-sensitive) data.  The log files are intentionally constructed to not include such information, even if it would be helpful to me to debug.  I take the security aspect seriously.  You are still encouraged to look through it if it calms your nerves, though most users may not have the background to know what' they're looking for.

After I see your log file, I would like to try to fix it and send it to you to try it.  I have not had this problem before, so I can't recreate the error to know if I've fixed it.  But based on what you already copied, I'm pretty sure I know what to do.

Your wallets are safe, just inaccessible.  Can you try something?  Can you go to the Start menu and find where Armory was installed, and then select "Armory (Offline)".  Tell me if that loads or if you get the same error.  If it loads, you can at least get access to your wallets where you could theoretically export the private keys to pull into a different applications.  But hopefully I'll get a fix for you shortly!

I sent you an email. Starting the offline version through the start menu gives me the same problem!

I will be waiting for your email. Thanks!