BitShares Forum
Main => Technical Support => Topic started by: iHashFury on January 17, 2016, 12:55:12 pm
-
error:
[2027:0117/131039:ERROR:browser_main_loop.cc(189)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[2054:0117/131040:INFO:renderer_main.cc(200)] Renderer process started
[2027:0117/131040:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[2027:0117/131040:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[2027:0117/131040:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[2027:0117/131040:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[2027:0117/131040:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[2027:0117/131040:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[2027:0117/131040:WARNING:accelerator_util.cc(185)] Invalid accelerator token: command
[2]+ Segmentation fault (core dumped) BitShares-light
Fix: downgrade to boost-1.59.0-5-x86_64
-
https://github.com/cryptonomex/graphene-ui/issues/675
-
I ran in to a boost 1.60 issue when working on RaiBlocks https://raiblocks.net perhaps you've hit the same. It looks like the hex number parsing for boost multiprecision has a bug. I filled a report https://svn.boost.org/trac/boost/ticket/11857 and it's been fixed but no service release yet so we had to downgrade to 1.59 as well or apply the patch.