Quote from: vikram on April 03, 2015, 07:16:20 PM

Quote from: liondani on April 02, 2015, 11:22:14 PM
default (locked) >>> wallet_unlock 888888
Continuing wallet upgrade...
Repairing key record     6091^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B
Repairing key record     91385Segmentation fault (!)
root@*******2:/home/bitshares/programs/client#


edit:
I can't unlock my wallet! Every time I try it it "upgrades" and is automatically repairing key records until the "Segmentation fault" error appears !!!

Do you still have a copy of this wallet? If so can you run it in debugger and get a stack trace of the crash?

will look at it but it is worth mentioning to tell that I had the same issue after that with the vps and after the segment fault on record 80000 I run the client again and somehow it made the upgrade successful...  it continued from the last record I think but counting from 1...

Sent from my ALCATEL ONE TOUCH 997D

Quote from: liondani on April 02, 2015, 11:22:14 PM
default (locked) >>> wallet_unlock 888888
Continuing wallet upgrade...
Repairing key record     6091^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B
Repairing key record     91385Segmentation fault (!)
root@*******2:/home/bitshares/programs/client#


edit:
I can't unlock my wallet! Every time I try it it "upgrades" and is automatically repairing key records until the "Segmentation fault" error appears !!!

Do you still have a copy of this wallet? If so can you run it in debugger and get a stack trace of the crash?

Quote from: liondani on April 02, 2015, 11:22:14 PM
default (locked) >>> wallet_unlock 888888
Continuing wallet upgrade...
Repairing key record     6091^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B
Repairing key record     91385Segmentation fault (!)
root@*******2:/home/bitshares/programs/client#


edit:
I can't unlock my wallet! Every time I try it it "upgrades" and is automatically repairing key records until the "Segmentation fault" error appears !!!

I managed to unlock the DVS wallet only after I deleted all files and restored an old wallet backup I had.
It only then repaired about 200,000 wallet records (!) successfully...  and it took some hours....

On trying the vote I get an error..

Quoteinvalid asset amount (35005) [show details]

[email protected]:38
○ [email protected]:46
○ [email protected]:47
○ [email protected]:40
○ [email protected]:41
○ [email protected]:9
○ [email protected]:9
○ [email protected]:7
○ [email protected]:7
○ app.js:9
○ [email protected]:3
○ [email protected]:3
35005 invalid_asset_amount: invalid asset amount

    {"share_string":"3198602.457349999808","max_rhs_size":5}
    bitshares  asset_record.cpp:93 share_string_to_satoshi

    {"share_string":"3198602.457349999808","precision":100000}
    bitshares  asset_record.cpp:109 share_string_to_satoshi

    {"amount":"3198602.457349999808"}
    bitshares  asset_record.cpp:114 asset_from_string

    {"amount":"3198602.457349999808","symbol":"DVS"}
    bitshares  chain_interface.cpp:241 to_ugly_asset

    {"amount_to_transfer":"3198602.457349999808","asset_symbol":"DVS","from_account_name":"davidpbrown","recipient":"davidpbrown","memo_message":"vote_all","strategy":"vote_all"}
    bitshares  wallet_api.cpp:322 wallet_transfer

    {}
    bitshares  common_api_client.cpp:3845 wallet_transfer

[hide details]

Quote from: liondani on April 03, 2015, 09:17:14 AM
Is it normal that it automatically repairs more than 180,0000 key records? (and counting....)

I've not seen that before and if I did I'd stop it and redownload the blockchain with --resync-blockchain

Is it normal that it automatically repairs more than 180,0000 key records? (and counting....)

default (locked) >>> wallet_unlock 888888
Continuing wallet upgrade...
Repairing key record     6091^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B
Repairing key record     91385Segmentation fault (!)
root@*******2:/home/bitshares/programs/client#


edit:
I can't unlock my wallet! Every time I try it it "upgrades" and is automatically repairing key records until the "Segmentation fault" error appears !!!

I still get notifications that seem to be x11+ of the same

QuoteJSON Parse error: Unterminated string [show details]

but then it shows no detail and it's unclear where those come from.


Incidentally, for the qt, I've got in the habit of doing

Quotesudo npm install -g lineman
sudo npm install

rather than just

Quotesudo npm install -g lineman
npm install

I wonder that second one works only on a faster machine where the sudo doesn't time out.

Quote from: kokojie on April 02, 2015, 03:19:21 AM

Quote from: clayop on April 02, 2015, 12:01:16 AM
Try https://github.com/BitShares/DevShares/blob/master/BUILD_UBUNTU.md

That's weird, I followed the steps in your link, and it worked. Was there something wrong in my old steps?

Quote from: liondani on April 02, 2015, 06:20:14 PM
on the last step (make)
I get this error:

Scanning dependencies of target bts_cli
[ 80%] Building CXX object libraries/cli/CMakeFiles/bts_cli.dir/cli.cpp.o
In file included from /home/liondani/DevShares/bitshares/libraries/client/include/bts/client/client.hpp:4:0,
                 from /home/liondani/DevShares/bitshares/libraries/cli/include/bts/cli/cli.hpp:4,
                 from /home/liondani/DevShares/bitshares/libraries/cli/cli.cpp:2:
/home/liondani/DevShares/bitshares/libraries/api/include/bts/api/reflect_api.hpp:6:22: fatal error: fc/api.hpp: No such file or directory
#include <fc/api.hpp>
                      ^
compilation terminated.
make[2]: *** [libraries/cli/CMakeFiles/bts_cli.dir/cli.cpp.o] Error 1
make[1]: *** [libraries/cli/CMakeFiles/bts_cli.dir/all] Error 2
make: *** [all] Error 2

any suggestions?

(I made like always the same steps   https://github.com/BitShares/DevShares/blob/master/BUILD_UBUNTU.md )

fc now has a submodule so we have nested submodules. Easiest way to sync up submodules is in root project do "git submodule update --init --recursive" as build instructions now say.

on the last step (make)
I get this error:

Scanning dependencies of target bts_cli
[ 80%] Building CXX object libraries/cli/CMakeFiles/bts_cli.dir/cli.cpp.o
In file included from /home/liondani/DevShares/bitshares/libraries/client/include/bts/client/client.hpp:4:0,
                 from /home/liondani/DevShares/bitshares/libraries/cli/include/bts/cli/cli.hpp:4,
                 from /home/liondani/DevShares/bitshares/libraries/cli/cli.cpp:2:
/home/liondani/DevShares/bitshares/libraries/api/include/bts/api/reflect_api.hpp:6:22: fatal error: fc/api.hpp: No such file or directory
#include <fc/api.hpp>
                      ^
compilation terminated.
make[2]: *** [libraries/cli/CMakeFiles/bts_cli.dir/cli.cpp.o] Error 1
make[1]: *** [libraries/cli/CMakeFiles/bts_cli.dir/all] Error 2
make: *** [all] Error 2

any suggestions?

(I made like always the same steps   https://github.com/BitShares/DevShares/blob/master/BUILD_UBUNTU.md )

I like the blockchain download progress bar in the gui. The bar started in the negative numbers though, and reached zero at the halfway point before starting to count up. Otherwise a nice little feature that should help the experience for new users.

Quote from: xeroc ¯\_(ツ)_/¯ on April 02, 2015, 06:27:59 AM

Quote from: clayop on April 02, 2015, 03:25:30 AM
IMO Documentations for new UIA system should be updated

haha .. you  are funny ..
There still is absolutely ZERO documentation about the UIA system ... sadly

Right haha.. so, updated -> uploaded.

Quote from: clayop on April 02, 2015, 03:25:30 AM
IMO Documentations for new UIA system should be updated

haha .. you  are funny ..
There still is absolutely ZERO documentation about the UIA system ... sadly

Working good so far.

Win 8.1 8gb

IMO Documentations for new UIA system should be updated, especially wallet_uia_update_authority_permissions and wallet_uia_update_active_flags. I have no idea about these two commands.