|
Title: Bitcoin-qt goes unresponsive from options (fixed I guess) Post by: fasti on February 09, 2014, 05:35:29 PM Was about to try bitcoin payment on humble bundle. Didn't know what the "miner fee" part was all about so I was unsure if there would be any fee on my transaction. Went to options to see that my fee was at 0.000000000, pushed reset options. Went in options again because I didn't want to see the ui in my mother language. "Need to restart client until this option is in effect"... ok. I shut it down but didn't relaunch, instead I decided to update it to latest 0.8.6 (I had 0.8.5). After updating, I went into options again as it was in crappy language. Now it will always go into unresponsive-mode after pressing "ok"(even if I didn't change anything, apply greyed) or "apply", cancel works correctly. Giving it tens of minutes didn't work either, I press the "x" and windows wants to shut it down forcefully.
Stuff that doesn't work: - Reinstalling latest version - Uninstaller(or windows uninstall, same thing I guess) - Deleting roaming\bitcoin (I have backup) - Deleting everything "bitcoin"-related with regedit - Restarting PC - Trying installing with different user Stuff that does work: - Installing version 0.8.1 or older (0.8.2 or later doesn't seem to work) I did notice that from 0.8.1 to 0.8.2 the installer-icon has changed : ) If that has to do with anything. So atm if I want to change any settings in options, I need to install 0.8.1 to change them, then install latest bitcoin-qt back. Otherwise it seems to work fine, it's finding peers and collecting data. But I don't even want to use this software for finance stuff as it's not working fully. I have changed settings many times after 0.8.2 in the past, but for some reason after updating to 0.8.6 it doesn't work anymore. Using Windows 8.0. How to fix? Title: Re: Bitcoin-qt goes unresponsive from options Post by: fasti on February 09, 2014, 07:38:17 PM If I block the internet from bitcoin-qt, changing the settings works, but there's still ~5secs of unresponsiveness. So then I checked out what it wrote in debug.log after it got up again:
2014-02-09 19:21:57 No valid UPnP IGDs found 2014-02-09 19:21:57 upnp thread exit 2014-02-09 19:21:57 upnp thread start So I disabled upnp and it now works like normal. Fixed I guess... |