Official Ubuntu builds

[hammurabi]

Update: I set up an amd64 DO droplet and VNCed into it to see if I could reproduce this. However, other bugs came up related to buggy VNC set-up that stopped me from really pursuing it.

I also found that commits were made to bitshares after the release was tagged but before binaries were released, so it is possible these bugs were already fixed:
https://github.com/BitShares/bitshares/compare/v0.4.24...master

I'll keep trying to reproduce these errors, but in the mean time I'm building the PPA to include the recent commits.

System automatically catch up the ppa update,
unfortunately after updating nothing changed in regard to the reported errors.
JSON Parse errors and Not connected message still persists.

I am still about to investigate deeper by playing with different network setup.


@josojo question:
I haven't transacted any bitUSD. This is rather irrelevant since these parsing bugs show up even on empty wallet.
My market menu shows everything at 0.00. So I guess some bugs must be there as well.

[maqifrnswa]

Update: I set up an amd64 DO droplet and VNCed into it to see if I could reproduce this. However, other bugs came up related to buggy VNC set-up that stopped me from really pursuing it.

I also found that commits were made to bitshares after the release was tagged but before binaries were released, so it is possible these bugs were already fixed:
https://github.com/BitShares/bitshares/compare/v0.4.24...master

I'll keep trying to reproduce these errors, but in the mean time I'm building the PPA to include the recent commits.

[maqifrnswa]

I installed from PPA using a clean libvrt (KVM) virtual machine on i386 guest and i386 host with both 14.04 and 14.10, no problems or issues. I don't have amd64 host kernel (I have an old i386 kernel on an amd64 architecture), so I still can't reproduce these errors. I'll try burning a livecd and installing from there.

It seems like this only an issue only on amd64

[josojo]

Hey guys,

I have the same problems with my ubuntu 14.10 build on amd64.
I have also the following findings:
a) Still receiving (116 error instances after 5 minutes):
'JSON Parse error: Property name must be a string literal [show details]'
b) Clicking 'show details' doesn't do anything.
c) 'Not connected'
and
d) That some funds have been send to 'Unknown'.

These funds, which have been send to 'Unknown' were all market orders. I was buying bitusd. Maybe there is link between the JSON Parse error and the market orders. I have never looked deeply under the hood of bitshares, thus I can not evaluate whether there could be a possible link. But I want  to mention it here at least.

Hammurabi, do you have also some bitusd in your account?

[hammurabi]

i just installed BitShares from PPA on 14.10 with an i386 architecture with no problems. Next step I'll make some clean virtual machines and test it there. Hopefully something breaks so we can figure out what is wrong...

Thanks! Looking forward to see the results.
If you have any idea what else I could test feel free to mention it :)

I am now going to test again with some environmental changes. Like network setup (uPNP?!)
Until now test were performed in similar network environment and using only intel processors.

[maqifrnswa]

i just installed BitShares from PPA on 14.10 with an i386 architecture with no problems. Next step I'll make some clean virtual machines and test it there. Hopefully something breaks so we can figure out what is wrong...

[jamesc]

You might find more info in the browser console too..

[hammurabi]

amd64... that narrows it down, I've been testing on i386
thanks for your help hunting this down!

Unfortunately on Ubuntu 14.10 i386 Bitshares doesn't work correctly.
VirtualBox 14.04.1 x64 Host, 14.10 i386 guest.
Linux test 3.16.0-23-generic #31-Ubuntu SMP i686 i68 i686 GNU/Linux

a) Still receiving (116 error instances after 5 minutes):
'JSON Parse error: Property name must be a string literal [show details]'
b) Clicking 'show details' doesn't do anything.
c) 'Not connected'


Below some useful tips for VirtualBox users:
During installation pressing RCTRL+1, RCTRL+7 restarts the screen in case it gets locked when installer changes screen mode.

Code Select Expand

sudo apt-get install virtualbox-guest-dkms (after restarting you will be able to increase screen resolution)

[maqifrnswa]

amd64... that narrows it down, I've been testing on i386
thanks for your help hunting this down!

[hammurabi]

One more thing, maybe try:

Code Select Expand

$ mv peers.leveldb peers.levedb.old
$ mkdir old
$ mv *.json old

and let the client rebuild them?

Code Select Expand

$ bitshares_client --version
{
  "blockchain_name": "BitShares",
  "blockchain_description": "The Future of Banking",
  "client_version": "v0.4.24",
  "bitshares_toolkit_revision": "377b57766dfa07e9a95952503217de31636ab9ee",
  "bitshares_toolkit_revision_age": "52 hours ago",
  "fc_revision": "e6b43a6149b8974ba1d3f683b9e01916a841c1de",
  "fc_revision_age": "71 hours ago",
  "compile_date": "compiled on Nov 12 2014 at 00:56:33",
  "boost_version": "1.54",
  "openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
  "build": "linux 64-bit"
}



After moving *.json to old directory and renaming peers.leveldb.old json parsing errors still persist.
Except I was asked to re-download the recent update from within the Bitshares gui client.

So it happens on:
1. Core i7 Ubuntu 14.04.1 LTS AMD64  (3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux)
2. Inside default VirtualBox 14.10 AMD64 (fresh install, only basic gfx guest extension added for bigger than 640x480 resolution)
3. KVM Guest 14.10 AMD64 (almost fresh install)


I will test 32-bit in a moment or two..

[maqifrnswa]

One more thing, maybe try:

Code Select Expand

$ mv peers.leveldb peers.levedb.old
$ mkdir old
$ mv *.json old

and let the client rebuild them?

[maqifrnswa]

thanks for pointing it out, I can't reproduce it however. My version just loads fine, can log in and operate normally.

What architecture and Ubuntu version are you on?

Code Select Expand


$ bitshares_client --version
{
  "blockchain_name": "BitShares",
  "blockchain_description": "The Future of Banking",
  "client_version": "v0.4.24",
  "bitshares_toolkit_revision": "377b57766dfa07e9a95952503217de31636ab9ee",
  "bitshares_toolkit_revision_age": "51 hours ago",
  "fc_revision": "e6b43a6149b8974ba1d3f683b9e01916a841c1de",
  "fc_revision_age": "70 hours ago",
  "compile_date": "compiled on Nov 12 2014 at 00:56:38",
  "boost_version": "1.54",
  "openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
  "build": "linux 32-bit"
}

EDIT: I see you are on utopic (14.10), I don't have that... so perhaps there's something there... I'll look into that

[hammurabi]

To me it seems the GUI (more precisely, the web_wallet) was not compiled properly

It was confirmed by 'nathanhourt' at issue #67 to be related to web_wallet component.
https://github.com/BitShares/qt_wallet/issues/67

The bug was redirected to web_wallet repository as issue #420
https://github.com/BitShares/web_wallet/issues/420

Coder 'valzav' closed it as difficult to replicate. I have just replicated the bug in three simple steps:
- installed fresh Ubuntu 14.10 into VirtualBox
- added the ppa and installed bitshares
- run Bitshares
After unlocking the wallet issue 'JSON parsing errors' and issue 'Not connected' showed themselves right away.

[xeroc]

To me it seems the GUI (more precisely, the web_wallet) was not compiled properly

[chsln]

The same happens to me. From the package from PPA and as well if I build myself as I posted here https://bitsharestalk.org/index.php?topic=11237.0

I'm starting to think that we might miss a dependency or something.