All users, please upgrade your client version to 0.4.4

[wackou]

also, since around 0.4 or 0.4.2 (not 100% sure) my delegate seems to have a really hard time acquiring connections at the beginning. Starts with the 7-8 seed nodes it gets at the very beginning, then stays there for quite a while. Sometimes it takes off, but sometimes it just drops. Was at 3 connections just a couple of minutes ago, when I have:

Code Select Expand

(unlocked) >>> network_get_advanced_node_parameters
{
  "peer_connection_retry_timeout": 30,
  "desired_number_of_connections": 100,
  "maximum_number_of_connections": 200
}

[wackou]

I've had two crashes in the last 4 hours.  First one didn't have gdb running,  Second crash bt is

Had a similar crash 2 days ago, and today another one kind of similar too: https://github.com/BitShares/bitshares_toolkit/issues/649

[puppies]

anybody can help?

after

Code Select Expand


npm install


these errors occur and I can't continue making the gui for linux  :(

Code Select Expand


> [email protected] postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js

sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! weird error 127
npm ERR! not ok code 0


Sudo apt-get install nodejs-legacy

[maqifrnswa]

anybody can help?

after

Code Select Expand


npm install


these errors occur and I can't continue making the gui for linux  :(

Code Select Expand


> [email protected] postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js

sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! weird error 127
npm ERR! not ok code 0


ln -s /usr/bin/nodejs /usr/bin/node

or install the nodejs-legacy package instead of nodejs

Code Select Expand

$ apt-get install nodejs-legacy

[Riverhead]

Just leave it alone.  It takes a LONG time and appears to be doing nothing.  Just let it sit....can take hours on some hardware.

windows gui 0.4.4 is  stucked...

"Last block was synced 32d 17h 51m 30s ago "   and it goes up...

I deleted everything! (even wallet dir, appdata, all)
I put the .dll file on the right place...

8 network connections and it does not sync !!!



PS windows 7 32bit
PS2 no problems with linux server and delegates

[liondani]

windows gui 0.4.4 is  stucked...

"Last block was synced 32d 17h 51m 30s ago "   and it goes up...

I deleted everything! (even wallet dir, appdata, all)
I put the .dll file on the right place...

8 network connections and it does not sync !!!



PS windows 7 32bit
PS2 no problems with linux server and delegates

[Riverhead]

The icons are like a visual checksum to reduce your chances of sending funds to an incorrect account.

While the robots are cute I believe they are looking at other alternatives.

[nikauforest]

What is this icon bs?  http://robohash.org/ Did I download a legit client from github?

[nikauforest]

I just updated to 0.4.4

How do I get rid of the "cute" icons that appear next to my account name?

Any help would be appreciated. I do not want these robot icons.

[svk]

http://bitsharesblocks.com/#/blocks and http://x.bitmeat.com/ seem to be on minority forks

I upgraded bitsharesblocks yesterday, is it on the right one now? Still on vacation here..

[tonyk]

anybody can help?

after

Code Select Expand


npm install


these errors occur and I can't continue making the gui for linux  :(

Code Select Expand


> [email protected] postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js

sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! weird error 127
npm ERR! not ok code 0


ln -s /usr/bin/nodejs /usr/bin/node

[liondani]

anybody can help?

after

Code Select Expand


npm install


these errors occur and I can't continue making the gui for linux  :(

Code Select Expand


> [email protected] postinstall /home/liondani/bitsharesx/programs/web_wallet/node_modules/lineman-less
> node script/postinstall.js

sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! weird error 127
npm ERR! not ok code 0


[puppies]

I've had two crashes in the last 4 hours.  First one didn't have gdb running,  Second crash bt is

Code Select Expand

wallet (unlocked) >>>
Program received signal SIGSEGV, Segmentation fault.
get_tail (next=<synthetic pointer>, h=0x1e0)
    at /home/user/two/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
33          while( n->next_blocked_mutex ) {
(gdb) bt
#0  get_tail (next=<synthetic pointer>, h=0x1e0)
    at /home/user/two/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
#1  fc::mutex::unlock (this=this@entry=0x29a4948)
    at /home/user/two/bitsharesx/libraries/fc/src/thread/mutex.cpp:160
#2  0x00000000007b43f0 in ~scoped_lock (this=<synthetic pointer>,
    __in_chrg=<optimized out>)
    at /home/user/two/bitsharesx/libraries/fc/include/fc/thread/scoped_lock.hpp:8
#3  bts::net::detail::message_oriented_connection_impl::send_message (
    this=0x29a4780, message_to_send=...)
    at /home/user/two/bitsharesx/libraries/net/message_oriented_connection.cpp:195
#4  0x00000000007b4a88 in bts::net::message_oriented_connection::send_message (
    this=this@entry=0x100c0108, message_to_send=...)
    at /home/user/two/bitsharesx/libraries/net/message_oriented_connection.cpp:267
#5  0x00000000007aa380 in bts::net::peer_connection::send_queued_messages_task
    (this=0x100c00a0)
    at /home/user/two/bitsharesx/libraries/net/peer_connection.cpp:178
#6  0x00000000007aaa7c in operator() (__closure=<optimized out>)
    at /home/user/two/bitsharesx/libraries/net/peer_connection.cpp:222
#7  fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::__lambda2>::run(void *, void *) (functor=<optimized out>,
---Type <return> to continue, or q <return> to quit---prQuit


Anything else needed before I close that screen?

[ebit]

The market is right?

[ebit]

Thanks for vote x.ebit