BitShares 0.4.27.1 - problems

[vikram]

This issue can be fixed with a GUI update, but unfortunately most people are on 0.4.27.1 which means their client will crash with the new update format. Perhaps we can make a 0.4.27.3 release with this fix in it.

Would this fix this https://bitsharestalk.org/index.php?topic=12519.msg166051#msg166051 ?

Yep!
We could do something tricky like enable the update very briefly so that you could update and then disable it again, if you have a big enough stake to make the vote worthwhile.

That sounds like I would just have the problem?
Disable the update again, how would that work?

Not if you upgrade to 0.4.27.2
And it's simple, we put the update up, you update, we take it back down so nobody else sees an update.

Does 0.4.27.2 fix some of the problems I posted in the OP?  I have jobs lined up (translation of BitShares 101 into Spanish + more) and can't withdraw any delegate pay.  I'm paralysed without a working client.

toast can give details on if he thinks some of those might be addressed, but I would guess that you will likely have to wait for the next release. if lots of people are having problems like this we can probably put out a hotfix release very quickly, otherwise we will try to do a full release fairly soon.

[matt608]

This issue can be fixed with a GUI update, but unfortunately most people are on 0.4.27.1 which means their client will crash with the new update format. Perhaps we can make a 0.4.27.3 release with this fix in it.

Would this fix this https://bitsharestalk.org/index.php?topic=12519.msg166051#msg166051 ?

Yep!
We could do something tricky like enable the update very briefly so that you could update and then disable it again, if you have a big enough stake to make the vote worthwhile.

That sounds like I would just have the problem?
Disable the update again, how would that work?

Not if you upgrade to 0.4.27.2
And it's simple, we put the update up, you update, we take it back down so nobody else sees an update.

Does 0.4.27.2 fix some of the problems I posted in the OP?  I have jobs lined up (translation of BitShares 101 into Spanish + more) and can't withdraw any delegate pay.  I'm paralysed without a working client.

[jsidhu]

So since I run my client often and then switch to GUI to test the BTS URI Scheme I noticed that after running the client for a while, shutting it down and then starting the GUI, I get the transaction error message where previously it was behaving... this leads to other problems like not being able to post transactions and syncing with the network. Why would the client and GUI have different ways to sync? I notice that if I start either after  a while even though the other is running it has to sync up with missing blocks from last time it ran.

[toast]

This issue can be fixed with a GUI update, but unfortunately most people are on 0.4.27.1 which means their client will crash with the new update format. Perhaps we can make a 0.4.27.3 release with this fix in it.

Would this fix this https://bitsharestalk.org/index.php?topic=12519.msg166051#msg166051 ?

Yep!
We could do something tricky like enable the update very briefly so that you could update and then disable it again, if you have a big enough stake to make the vote worthwhile.

That sounds like I would just have the problem?
Disable the update again, how would that work?

Not if you upgrade to 0.4.27.2
And it's simple, we put the update up, you update, we take it back down so nobody else sees an update.

[santaclause102]

This issue can be fixed with a GUI update, but unfortunately most people are on 0.4.27.1 which means their client will crash with the new update format. Perhaps we can make a 0.4.27.3 release with this fix in it.

Would this fix this https://bitsharestalk.org/index.php?topic=12519.msg166051#msg166051 ?

Yep!
We could do something tricky like enable the update very briefly so that you could update and then disable it again, if you have a big enough stake to make the vote worthwhile.

That sounds like I would just have the problem?
Disable the update again, how would that work?

[toast]

This issue can be fixed with a GUI update, but unfortunately most people are on 0.4.27.1 which means their client will crash with the new update format. Perhaps we can make a 0.4.27.3 release with this fix in it.

Would this fix this https://bitsharestalk.org/index.php?topic=12519.msg166051#msg166051 ?

Yep!
We could do something tricky like enable the update very briefly so that you could update and then disable it again, if you have a big enough stake to make the vote worthwhile.

[santaclause102]

This issue can be fixed with a GUI update, but unfortunately most people are on 0.4.27.1 which means their client will crash with the new update format. Perhaps we can make a 0.4.27.3 release with this fix in it.

Would this fix this https://bitsharestalk.org/index.php?topic=12519.msg166051#msg166051 ?

[toast]

This issue can be fixed with a GUI update, but unfortunately most people are on 0.4.27.1 which means their client will crash with the new update format. Perhaps we can make a 0.4.27.3 release with this fix in it.

[lzr1900]

Given up.shit-like wallet.

[cass]

I can't load the client... CLI syncs with network but the GUI says Failure during transaction scanning at the bottom.. this is blocking me from testing my cart stuff and is really annoying, i've redownloaded the blockchain twice by deleting everything but the wallets folder.

0.4.27.2 didn't help.

DO you've backup your wallet.json? If so,you should try to delete complete %bitshares/ folder and then restore after you installed fresh wallet!

[toast]

I can't load the client... CLI syncs with network but the GUI says Failure during transaction scanning at the bottom.. this is blocking me from testing my cart stuff and is really annoying, i've redownloaded the blockchain twice by deleting everything but the wallets folder.

0.4.27.2 didn't help.

Try it with a fresh wallet maybe, I can't see how else trx scanning can fail for you but not for everyone else

[jsidhu]

I can't load the client... CLI syncs with network but the GUI says Failure during transaction scanning at the bottom.. this is blocking me from testing my cart stuff and is really annoying, i've redownloaded the blockchain twice by deleting everything but the wallets folder.

0.4.27.2 didn't help.

[emski]

I am aware of the issues.  It is frustrating me as well.

@bytemaster What happened to the PR that was going to review all your non-technical forum posts ?

[santaclause102]

I too am having major problems with the v0.4.27.1 Qt client on Ubuntu.

First, everything is operating much more slowly. The pages take a long time to update. I literally wait seconds for the thumbs up/down button to react to the click.

Second, the UI is incredibly buggy. Sometimes it gets to a state where it won't respond/load the pages properly and I simply need to restart it.

I tried using the command line client, and it was surprisingly even worse. It lags so bad it is nearly impossible to type in commands (note that this is only after the wallet is unlocked and transaction scanning begins). The CPU usage is very minimal. It is using the hard disk, but it is nothing that out of the ordinary. Anyone else experiencing this problem?

same problem about slow reaction times with thumbs up etc. here until this happened: https://bitsharestalk.org/index.php?topic=7022.msg164927#msg164927

That problem I got resolved. But I can not vote. It just dosn't make a transfer when I click "update vote". And it freezes when I go to File > Quit.
Edit: The second time I was able to quit it but it too a while before it closed. Voting didn't work after restarting and trying again.

[oco101]

Given up !! Can't even update it , unusable for me ,,,

[Shentist]

it looks to me, that on the bitBTC market the short Order with 0.11% is not buyable. Tried it multiple times right now.

[pgbit]

A bit of patience has paid off. One thread suggested removing "peers.leveldb" and "chain" directories from the BitShares roaming subfolder. This caused a further crash on resync but after a few hours it has successfully reconnected syncing all blocks. Perhaps the wallet could have more user (noob) friendly tips displayed if it clearly isnt syncing, with suggested solutions.

[islandking]

I have given up trying to update and reupdate the client. Waiting for a stable client.

[pgbit]

I am aware of the issues.  It is frustrating me as well.

Quite a few "freezing episodes" on Windows, locking machine. I guess we wait for an update.

[bytemaster]

I am aware of the issues.  It is frustrating me as well. 

[liondani]

even after rescan and even a synchronized wallet,when I type commands the characters show up after seconds ... (cli client )... It seems better after a couple of minutes...

Sent from my ALCATEL ONE TOUCH 997D

[santaclause102]

I too am having major problems with the v0.4.27.1 Qt client on Ubuntu.

First, everything is operating much more slowly. The pages take a long time to update. I literally wait seconds for the thumbs up/down button to react to the click.

Second, the UI is incredibly buggy. Sometimes it gets to a state where it won't respond/load the pages properly and I simply need to restart it.

I tried using the command line client, and it was surprisingly even worse. It lags so bad it is nearly impossible to type in commands (note that this is only after the wallet is unlocked and transaction scanning begins). The CPU usage is very minimal. It is using the hard disk, but it is nothing that out of the ordinary. Anyone else experiencing this problem?

same problem about slow reaction times with thumbs up etc. here until this happened: https://bitsharestalk.org/index.php?topic=7022.msg164927#msg164927

[arhag]

I too am having major problems with the v0.4.27.1 Qt client on Ubuntu.

First, everything is operating much more slowly. The pages take a long time to update. I literally wait seconds for the thumbs up/down button to react to the click.

Second, the UI is incredibly buggy. Sometimes it gets to a state where it won't respond/load the pages properly and I simply need to restart it.

I tried using the command line client, and it was surprisingly even worse. It lags so bad it is nearly impossible to type in commands (note that this is only after the wallet is unlocked and transaction scanning begins). The CPU usage is very minimal. It is using the hard disk, but it is nothing that out of the ordinary. Anyone else experiencing this problem?

[matt608]

On Macos 10.9.5

problems:

- won't load market in delegate account, says 0 volume from my delegate account and freezes but sometimes loads ok in my normal user account
- client often freezes and is slow, especially in my delegate account.
- can't change account name from within a market (which shows 0 volume), have to go back to 'my accounts'
- accounts disappear sometimes from 'my accounts'
- won't lock or quit, have to force quit (sometimes)
- required 3 client restarts to for blockchain to sync
- clicked 'unapprove all' while client was frozen accidentally in frustration... now I have to go and approve 100+ delegates one by one again.
- "my votes" shows nothing even though I've voted a bunch of times.
- can't toggle approval, it goes darker blue then if I toggle approval for another delegate it goes darker blue for them instead and goes back to light blue for the one I just approved.  So can't actually vote.
- After broadcasting a transaction, block chain starts syncing backwards (3mins, 4mins, 5 mins), bar at the bottom turns a dark yellow and says "Caution | Last block was synced 3m 50s ago".  Solved by restarting client.

I just kept restarting and was able to send a transaction but it wasn't pretty and I still can't vote.

What to do?  Is everyone dealing with a barely functioning client at the moment?