0 Members and 1 Guest are viewing this topic.
Any chance to reduce memory requirements for compiling on linux to something below 2gb?
Quote from: Bitcoinfan on December 13, 2014, 07:58:04 pmI'm stuck on block 1253613. User that upgraded from .04.24Anyone have any thoughts of how to fix this from the GUI? I've rescanned many times and have 1 or 2 connections, but it still saying catch-up.
I'm stuck on block 1253613. User that upgraded from .04.24
>> blockchain_market_order_book BTC BTS BIDS (* Short, + Relative, - Relative Limit) | ASKS TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------0.10000000 BTC 2,399.99998 BTS 0.000041666667 BTC | 0.000049427372 BTC 2,199.17962 BTS 0.10869966 BTC0.17671190 BTC 120.42254 BTS 0.000040176778 BTC*| 0.000049438991 BTC 2,199.17979 BTS 0.10872522 BTC0.09999999 BTC 2,493.33276 BTS 0.000040106957 BTC | 0.000050000000 BTC 2,000.00000 BTS 0.10000000 BTC
--- syncing with p2p network, 22042 blocks left to fetch--- in sync with p2p network--- there are now 19 active connections to the p2p network--- syncing with p2p network, 1524 blocks left to fetch--- in sync with p2p network--- syncing with p2p network, 583617 blocks left to fetch--- there are now 18 active connections to the p2p network--- in sync with p2p network--- syncing with p2p network, 158482 blocks left to fetch--- in sync with p2p network--- syncing with p2p network, 9323 blocks left to fetch--- there are now 19 active connections to the p2p network...
Attempts to update votes result in CPU peg and non responsiveness of thumb buttons.
Quote from: vikram on December 12, 2014, 08:23:20 pmCan someone confirm if they still cannot import an old wallet into 0.4.26? I've put another fix in place but would like someone who previously had the problem to confirm if it works for them.I can with 0.4.10 backup. (could not do so with 0.4.25 RC1)backup by - 0.4.24 RC1 - missing some funds (but have not tried anything regarding finding them aka regenerate keys or whatever) and current version 0.4.26 backup is fine (no issues).
Can someone confirm if they still cannot import an old wallet into 0.4.26? I've put another fix in place but would like someone who previously had the problem to confirm if it works for them.
In RC2 restore wallet backup created in 0.4.24 is not working
the scanning is so slow only 1 account in this wallet
Same issue with tonyk2, can't import backups. Also when I try to regenerate keys from my current wallet I get the message in second image...
"blockchain_head_block_timestamp": "2014-12-10T03:24:50", "wallet_last_scanned_block_timestamp": "2014-11-13T12:13:00", "wallet_scan_progress": "0.71 %",
"blockchain_head_block_timestamp": "2014-12-10T03:42:10", "wallet_last_scanned_block_timestamp": "2014-11-15T23:08:00", "wallet_scan_progress": "9.13 %",
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 9431 alt 20 0 2417664 727296 183268 D 1.0 19.4 7:34.47 bitshares_clien
Quote from: clayop on December 09, 2014, 07:35:21 amAccount-Key menu in GUI cannot work.To get the key in GUI, users have to use wallet_list_my_account in console.clayop, could you describe your issue a little bit more? Do you mean Keys tab on the account page won't? Maybe you could post a screenshot?
Account-Key menu in GUI cannot work.To get the key in GUI, users have to use wallet_list_my_account in console.
Quote from: Xeldal on December 09, 2014, 09:59:21 pmIs 0.4.25 RC1 meant to fix orphaned accounts?I had 1 prior to update, now I have 15.I saw your post (https://bitsharestalk.org/index.php?topic=9194.msg160105#msg160105 )--was going to wait for the final release to address it; but if you want to right now, you can try:Code: [Select](wallet closed) >>> h wallet_repair_recordsUsage:wallet_repair_records [collecting_account_name] tries to repair any inconsistent wallet account, key, and transaction recordstries to repair any inconsistent wallet account, key, and transaction recordsParameters: collecting_account_name (account_name, optional, defaults to ""): collect any orphan balances into this accountReturns: void
Is 0.4.25 RC1 meant to fix orphaned accounts?I had 1 prior to update, now I have 15.
(wallet closed) >>> h wallet_repair_recordsUsage:wallet_repair_records [collecting_account_name] tries to repair any inconsistent wallet account, key, and transaction recordstries to repair any inconsistent wallet account, key, and transaction recordsParameters: collecting_account_name (account_name, optional, defaults to ""): collect any orphan balances into this accountReturns: void
bitAsset:bitAsset markets are not working in the Windows GUI and were not working in 0.4.24 either. It's letting me submit orders, but the orders are not matching. Also, it says "insufficient feeds" at the top.
2. Cannot import older(originally save by v.0.4.10 and v.0.4.20)/other wallet. Imported successfully just before upgrading (client old ver was 0.4.24)
Interest for shorts can not be displayed in 0.4.25 wallet .
Quote from: cn-members on December 09, 2014, 07:42:02 amif I set lockscreen to 'flowers', it actually gives me nothing but this:I found it's address is:http://127.0.0.1:58770/img/logo-ico-blue.svgbut actually there is no such fileI think 'flowers' theme files were not included into the gui package. Will be fixed in 0.4.25 release version.
if I set lockscreen to 'flowers', it actually gives me nothing but this:I found it's address is:http://127.0.0.1:58770/img/logo-ico-blue.svgbut actually there is no such file
Could that have been from the bad key?
Window version wallet occupies a lot of memory and CPU percentage, making the computer extremely slow.