0 Members and 1 Guest are viewing this topic.
Did you ever work this out? Possible by doing a fresh install of 0.5.3 to import the backup, and then upgrading in-place to the latest version?
win764 Another corrupted wallet. I'm not able to open the wallet. Not able to import any backups.Code: [Select]10001 level_map_open_failure: level_map open failureFailure opening database: C:/Users/John/AppData/Roaming/BitShares/wallets/defaultStatus: Corruption: error in middle of record {"db":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","msg":"Corruption: error in middle of record"} th_a level_map.hpp:68 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::open {"dir":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","create":true,"cache_size":0} th_a level_map.hpp:73 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::openError opening wallet file C:/Users/John/AppData/Roaming/BitShares/wallets/default {"file":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"} th_a wallet_db.cpp:186 bts::wallet::wallet_db::openUnable to open wallet C:/Users/John/AppData/Roaming/BitShares/wallets/default {"wallet_file_path":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"} th_a wallet.cpp:753 bts::wallet::detail::wallet_impl::open_file {"wallet_name":"default"} th_a wallet.cpp:1075 bts::wallet::wallet::open {} th_a common_api_client.cpp:2861 bts::rpc_stubs::common_api_client::wallet_open {"command":"wallet_open"} th_a cli.cpp:626 bts::cli::detail::cli_impl::execute_commandGui errors out on trying to import any backup saying "invalid password" and crashes if you try to export.
10001 level_map_open_failure: level_map open failureFailure opening database: C:/Users/John/AppData/Roaming/BitShares/wallets/defaultStatus: Corruption: error in middle of record {"db":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","msg":"Corruption: error in middle of record"} th_a level_map.hpp:68 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::open {"dir":"C:/Users/John/AppData/Roaming/BitShares/wallets/default","create":true,"cache_size":0} th_a level_map.hpp:73 bts::db::level_map<int,struct bts::wallet::generic_wallet_record>::openError opening wallet file C:/Users/John/AppData/Roaming/BitShares/wallets/default {"file":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"} th_a wallet_db.cpp:186 bts::wallet::wallet_db::openUnable to open wallet C:/Users/John/AppData/Roaming/BitShares/wallets/default {"wallet_file_path":"C:/Users/John/AppData/Roaming/BitShares/wallets/default"} th_a wallet.cpp:753 bts::wallet::detail::wallet_impl::open_file {"wallet_name":"default"} th_a wallet.cpp:1075 bts::wallet::wallet::open {} th_a common_api_client.cpp:2861 bts::rpc_stubs::common_api_client::wallet_open {"command":"wallet_open"} th_a cli.cpp:626 bts::cli::detail::cli_impl::execute_command
Quote from: vlight on March 10, 2015, 07:36:32 pmSometimes when i click on BitUSD:BTS featured market it opens BitSILVER:BTS instead. (Windows 7 64 bit)Did you try to upgrade to newer wallet version? As far as I remember 0.6.0 had this bug and it's definitely should be fixed in 0.6.2.Don't forget to click Check for GUI updates in the main menu after you install it.
Sometimes when i click on BitUSD:BTS featured market it opens BitSILVER:BTS instead. (Windows 7 64 bit)
Yesterday one of my wallets got corrupted. It had been open + unlocked for a couple of days. When I tried shut down the client I had to kill it, apparently one thread was stuck in a loop or something. After restarting, I couldn't open the wallet anymore. The attempt fails with something about a checksum mismatch. One possible cause is that the partition where the wallet is stored became full at some point in time (but the client never gave me an error message and continued to work just fine while it was running).Importing an old backup + regenerating keys restored my balances completely AFAICT, only the tx history shows me many UNKNOWNs in market orders.
Quote from: Brekyrself on March 09, 2015, 05:37:39 pmQuote from: marcelus on March 09, 2015, 03:27:27 pmNot sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights? Not sure of the file structure on OSx however to get around this on Windows you can simply delete the "chain" folder located at /User/AppData/Roaming/BitShares. This will cause the wallet to re-sync. As a precaution when deleting anything, backup your wallet first!I know how to do this on a mac and have a backup. Will try it now. Cheers.
Quote from: marcelus on March 09, 2015, 03:27:27 pmNot sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights? Not sure of the file structure on OSx however to get around this on Windows you can simply delete the "chain" folder located at /User/AppData/Roaming/BitShares. This will cause the wallet to re-sync. As a precaution when deleting anything, backup your wallet first!
Not sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?
Quote from: marcelus on March 09, 2015, 03:27:27 pmNot sure if this is the right place to post this but I've just downloaded 0.6.2 for OSX. It can't seem to download past block 1138847. I remember having this issue before but it was due to the fact I didn't have the latest version. Any insights?Leave the client open for some hours or so .. I guess it will catch up by that time
Quote from: Xeldal on March 05, 2015, 10:45:45 pmwin7x64 v0.6.2I'm unable to send to any name with a dot in it. Once I enter the dot the box turns red and no matter what I type next it stays red and cannot send anything.This is a new wallet and a new account, same machine different data-dir. At least the transaction History works on this one. : (Can you check for GUI update in the menu? This should have been fixed in the most recent GUI update.
win7x64 v0.6.2I'm unable to send to any name with a dot in it. Once I enter the dot the box turns red and no matter what I type next it stays red and cannot send anything.This is a new wallet and a new account, same machine different data-dir. At least the transaction History works on this one. : (
Quote from: Xeldal on March 04, 2015, 06:09:40 pmI can send you what i have of course , Other than a negative balance, and a memo field with this in it " ┐╢╔►╛┘t\Y²ΦìδÑ.µqu# " I'm not seeing anything else unusual, at a glance.The transaction with the strange memo, evidently I sent a bunch of BTS to clout-delegate1, I don't remember doing this, but I have a terrible memory.That strange memo could be problematic.. I am assuming that is not a real memo you wrote--looks like a memo that seemed to decrypt so it shows up but not really so it shows garbage. Maybe you can try doing "wallet_remove_transaction <transacion_id>" for that particular transaction?
I can send you what i have of course , Other than a negative balance, and a memo field with this in it " ┐╢╔►╛┘t\Y²ΦìδÑ.µqu# " I'm not seeing anything else unusual, at a glance.The transaction with the strange memo, evidently I sent a bunch of BTS to clout-delegate1, I don't remember doing this, but I have a terrible memory.
Looks like backend is feeding poorly formatted json data into the GUI.Do you have access to cli client on this machine? If you do, could you run the following commands in it and look at json output:> eable_raw> history xeldal2Also do you have any estimation on how many transactions you might have for this account? It can be that there is some limit in QT's json parser implementation on a size of input data.Thank you!
Quote from: valzav on March 03, 2015, 10:27:49 pmQuote from: Xeldal on March 03, 2015, 08:28:31 pmQuote from: valzav on March 03, 2015, 08:17:45 pmI guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.How is this done? Clicking on "show details" doesn't seem to do anything .Probably this error doesn't have any details. Do you have access to the log files? If you do, could look if default.log references this error?This is from the default.log file after I try and initiate "history xeldal2" from the console.Code: [Select]2015-03-04T00:26:12 th_a:?unnamed? log_message ] Message from GUI: js error: JSON Parse error: Unterminated stringparse@[native code] ○ S@http://127.0.0.1:59187/js/app.js:5:1792 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948 ○ http://127.0.0.1:59187/js/app.js:6:4375 ○ f@http://127.0.0.1:59187/js/app.js:4:59169 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357 ○ e@http://127.0.0.1:59187/js/app.js:6:9402 ○ i@http://127.0.0.1:59187/js/app.js:6:45333 ○ http://127.0.0.1:59187/js/app.js:6:45505 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806 ○ f@http://127.0.0.1:59187/js/app.js:6:15887 ○ r@http://127.0.0.1:59187/js/app.js:6:24666 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:352015-03-04T00:26:12 th_a:?unnamed? log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined) Utilities.cpp:352015-03-04T00:26:14 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:7322015-03-04T00:26:27 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:7322015-03-04T00:26:30 th_a:?unnamed? log_message ] Message from GUI: js error: JSON Parse error: Unterminated stringparse@[native code] ○ S@http://127.0.0.1:59187/js/app.js:5:1792 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948 ○ http://127.0.0.1:59187/js/app.js:6:4375 ○ f@http://127.0.0.1:59187/js/app.js:4:59169 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357 ○ e@http://127.0.0.1:59187/js/app.js:6:9402 ○ i@http://127.0.0.1:59187/js/app.js:6:45333 ○ http://127.0.0.1:59187/js/app.js:6:45505 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806 ○ f@http://127.0.0.1:59187/js/app.js:6:15887 ○ r@http://127.0.0.1:59187/js/app.js:6:24666 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:352015-03-04T00:26:30 th_a:?unnamed? log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined) Utilities.cpp:352015-03-04T00:26:34 ntp:request_time_task request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:772015-03-04T00:26:34 ntp:request_time_task request_now ] sending request to 66.175.209.17:123 ntp.cpp:812015-03-04T00:26:34 ntp:ntp_read_loop read_loop ] received ntp reply from 66.175.209.17:123 ntp.cpp:1472015-03-04T00:26:34 ntp:ntp_read_loop read_loop ] ntp offset: -3039805, round_trip_delay 137967 ntp.cpp:1612015-03-04T00:26:34 ntp:ntp_read_loop read_loop ] ntp_delta_time updated to -3039805 ntp.cpp:177
Quote from: Xeldal on March 03, 2015, 08:28:31 pmQuote from: valzav on March 03, 2015, 08:17:45 pmI guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.How is this done? Clicking on "show details" doesn't seem to do anything .Probably this error doesn't have any details. Do you have access to the log files? If you do, could look if default.log references this error?
Quote from: valzav on March 03, 2015, 08:17:45 pmI guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.How is this done? Clicking on "show details" doesn't seem to do anything .
I guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.
2015-03-04T00:26:12 th_a:?unnamed? log_message ] Message from GUI: js error: JSON Parse error: Unterminated stringparse@[native code] ○ S@http://127.0.0.1:59187/js/app.js:5:1792 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948 ○ http://127.0.0.1:59187/js/app.js:6:4375 ○ f@http://127.0.0.1:59187/js/app.js:4:59169 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357 ○ e@http://127.0.0.1:59187/js/app.js:6:9402 ○ i@http://127.0.0.1:59187/js/app.js:6:45333 ○ http://127.0.0.1:59187/js/app.js:6:45505 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806 ○ f@http://127.0.0.1:59187/js/app.js:6:15887 ○ r@http://127.0.0.1:59187/js/app.js:6:24666 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:352015-03-04T00:26:12 th_a:?unnamed? log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined) Utilities.cpp:352015-03-04T00:26:14 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:7322015-03-04T00:26:27 bitshares:rebroadcast_pending rebroadcast_pending_ ] rebroadcasting 0 client.cpp:7322015-03-04T00:26:30 th_a:?unnamed? log_message ] Message from GUI: js error: JSON Parse error: Unterminated stringparse@[native code] ○ S@http://127.0.0.1:59187/js/app.js:5:1792 ○ ec@http://127.0.0.1:59187/js/app.js:6:3948 ○ http://127.0.0.1:59187/js/app.js:6:4375 ○ f@http://127.0.0.1:59187/js/app.js:4:59169 ○ ic@http://127.0.0.1:59187/js/app.js:6:4357 ○ e@http://127.0.0.1:59187/js/app.js:6:9402 ○ i@http://127.0.0.1:59187/js/app.js:6:45333 ○ http://127.0.0.1:59187/js/app.js:6:45505 ○ $eval@http://127.0.0.1:59187/js/app.js:6:81532 ○ $digest@http://127.0.0.1:59187/js/app.js:6:80046 ○ $apply@http://127.0.0.1:59187/js/app.js:6:81806 ○ f@http://127.0.0.1:59187/js/app.js:6:15887 ○ r@http://127.0.0.1:59187/js/app.js:6:24666 ○ onload@http://127.0.0.1:59187/js/app.js:6:25206 Utilities.cpp:352015-03-04T00:26:30 th_a:?unnamed? log_message ] Message from GUI: rpc error: JSON Parse error: Unterminated string (undefined) Utilities.cpp:352015-03-04T00:26:34 ntp:request_time_task request_now ] resolving... ["pool.ntp.org",123] ntp.cpp:772015-03-04T00:26:34 ntp:request_time_task request_now ] sending request to 66.175.209.17:123 ntp.cpp:812015-03-04T00:26:34 ntp:ntp_read_loop read_loop ] received ntp reply from 66.175.209.17:123 ntp.cpp:1472015-03-04T00:26:34 ntp:ntp_read_loop read_loop ] ntp offset: -3039805, round_trip_delay 137967 ntp.cpp:1612015-03-04T00:26:34 ntp:ntp_read_loop read_loop ] ntp_delta_time updated to -3039805 ntp.cpp:177
Quote from: Xeldal on March 03, 2015, 04:12:11 pmYes fully synced.. version 0.6.2 Win7x64It works for other accounts in the same client... just not that one.125 JSON March 3, 2015 at 11:13:25 AM ESTParse error: Unterminated stringI guess "Parse error: Unterminated string" is shown in the top right corner under the bell sign? Can you expand this error and send me the stack trace? Thank you.
Yes fully synced.. version 0.6.2 Win7x64It works for other accounts in the same client... just not that one.125 JSON March 3, 2015 at 11:13:25 AM ESTParse error: Unterminated string
Quote from: Xeldal on March 03, 2015, 03:46:50 pmAccount history inaccessible. No account transaction history is viewable in any account from the GUI pages. Reload does nothing. Only some of my accounts history is accessible from Console .... for example entering "history xeldal2" produces nothing. It just sits there.Is it fully synchronized? What is your OS and wallet version?
Account history inaccessible. No account transaction history is viewable in any account from the GUI pages. Reload does nothing. Only some of my accounts history is accessible from Console .... for example entering "history xeldal2" produces nothing. It just sits there.
Quote from: oco101 on March 02, 2015, 04:21:30 amQuote from: onceuponatime on March 01, 2015, 11:03:11 pmQuote from: oco101 on February 27, 2015, 11:28:58 pmI manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. ThanksI am having the same problem. Can't log in.Let me know if you find a fix. I'm thinking to go back to the wallet backup and reinstall everything .....againI just deleted everything but the wallet folder and reinstalled. Same problem.
Quote from: onceuponatime on March 01, 2015, 11:03:11 pmQuote from: oco101 on February 27, 2015, 11:28:58 pmI manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. ThanksI am having the same problem. Can't log in.Let me know if you find a fix. I'm thinking to go back to the wallet backup and reinstall everything .....again
Quote from: oco101 on February 27, 2015, 11:28:58 pmI manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. ThanksI am having the same problem. Can't log in.
I manage to install 0.6.2 and it was working then my computer crashed (not related to bitshares). I restarted the computer and then when I try to long in my Bitshares I have 3 moving dots that are going for a few seconds and then nothing happened it does not say the password is not good. So I did uninstall everything delete everything except the wallet folder, reinstalled Bitshares but I got the same behavior when I try to log on. So basically no matter what I do I can't no longer log in my wallet. Not sure if this has to go to technical support area or it just happened in 0.6.2, but any help would be appreciated. Thanks
1. In the Exchange, when I first click the bitUSD:BTS chart it open the bitSILVER:BTS trading, then it hang and crash afterwards.2. I sold all the amount of coins and it keep some dust0.000001 CFSGOLD0.000001 GOLD0.0001 SILVER
Quote from: ubits on February 26, 2015, 08:25:22 pmI have used almost every version of the wallet form the beginning with few issues. Starting with 0.61 lost account names, balances and transactions0.62 blockchain synced quickly, under an hour, and account names show, but no balances or transactionsMavericks, fully synced 0.62Do balances and transactions return when you right click and select reload?
I have used almost every version of the wallet form the beginning with few issues. Starting with 0.61 lost account names, balances and transactions0.62 blockchain synced quickly, under an hour, and account names show, but no balances or transactionsMavericks, fully synced 0.62
win7x64can't change accounts in top right from any of the tabs.Only place it works is inside a market trading page.
One suggestion from the chinese community: the content of app.js.map is in plain text, it can be compressed and cached locally to save the bandwidth. On the other hand, I also think the identicon is great, and I wonder whether the identicon can be used in reverse: input the identicon figure and it can be reversed into an account name? I found some discussion elsewhere and guess it is possible right? I think it could be great if we can use mobile wallet to scan identicon and complete transaction.
Whats the name of the tag in the public.data field to switch titan/non-titan?
Robohashes have been replaced with more reliable Identicons
Blockchain history will be replayed on upgrade