BitShares Forum
Main => Technical Support => Topic started by: hammurabi on November 01, 2014, 04:07:05 am
-
I would like to "vote" on maintaining official ubuntu build/ppa/something with GUI.
For competitors it isn't a big deal. Somehow for bitsharesx it is!
Some says that maintainers cannot be trusted thus we have to compile for ourselves. But at the same time windows binaries are happily being put out for downloading. That is a heresy:)
As I recall there was a quite fat (2000pts) bounty on autobuild with Jenkins feature. Was this brilliant idea scrapped already?
-
http://jenkins.bitshares.org/
Not sure who's maintaining it though ..
With the changes to the superDAC this will hopefully be reactivated .. until then BTSX is totally separated from I3 and managed by DacSunLimited .. We have no clue why they don't publish packages for ubuntu :(
-
I've offered to help them set up secure auto-builders and PPAs, but they don't seem to be interested. See my PPA in my signature for packages. As for whether or not you can trust me, you already do if you run Ubuntu or Debian.I have direct upload access to Debian and Ubuntu directly takes my packages from Debian and ships them in Ubuntu. You are already running my packages on your system for some crucial libraries (e.g., zlib). I posted a signed message in my delegate thread that is signed with the same key that is already on your machine (if you run Debian, otherwise you can install it by installing "debian-keyring" in ubuntu).
-
I've offered to help them set up secure auto-builders and PPAs, but they don't seem to be interested. See my PPA in my signature for packages. As for whether or not you can trust me, you already do if you run Ubuntu or Debian.I have direct upload access to Debian and Ubuntu directly takes my packages from Debian and ships them in Ubuntu. You are already running my packages on your system for some crucial libraries (e.g., zlib). I posted a signed message in my delegate thread that is signed with the same key that is already on your machine (if you run Debian, otherwise you can install it by installing "debian-keyring" in ubuntu).
Thank You for the work done on both Bitshares PPA and Debian.
Will surely delegate You as soon as I get this gui client working :)
In fact I have already sourced your ppa into my system.
But there is only cli tool and no GUI version to please my laziness.
(I believe there are many like me. I could have been using bitshares but since there is no ready-to-use tool I just don't).
I hope 'dacsunlimited' will recognize your fruitful efforts and agree to incorporate your auto-builders.
If they don't it will be a clear message that they are doing a sabotage on the project!
-
I've offered to help them set up secure auto-builders and PPAs, but they don't seem to be interested. See my PPA in my signature for packages. As for whether or not you can trust me, you already do if you run Ubuntu or Debian.I have direct upload access to Debian and Ubuntu directly takes my packages from Debian and ships them in Ubuntu. You are already running my packages on your system for some crucial libraries (e.g., zlib). I posted a signed message in my delegate thread that is signed with the same key that is already on your machine (if you run Debian, otherwise you can install it by installing "debian-keyring" in ubuntu).
Thank You for the work done on both Bitshares PPA and Debian.
Will surely delegate You as soon as I get this gui client working :)
In fact I have already sourced your ppa into my system.
But there is only cli tool and no GUI version to please my laziness.
(I believe there are many like me. I could have been using bitshares but since there is no ready-to-use tool I just don't).
I hope 'dacsunlimited' will recognize your fruitful efforts and agree to incorporate your auto-builders.
If they don't it will be a clear message that they are doing a sabotage on the project!
OHHH! Thank you for pointing out the GUI isn't set up right... I'll fix it right now. The GUI is included, it was just installed in the wrong place...
-
I directed DSL to this thread. Thanks maqifrnswa.
-
I've offered to help them set up secure auto-builders and PPAs, but they don't seem to be interested. See my PPA in my signature for packages. As for whether or not you can trust me, you already do if you run Ubuntu or Debian.I have direct upload access to Debian and Ubuntu directly takes my packages from Debian and ships them in Ubuntu. You are already running my packages on your system for some crucial libraries (e.g., zlib). I posted a signed message in my delegate thread that is signed with the same key that is already on your machine (if you run Debian, otherwise you can install it by installing "debian-keyring" in ubuntu).
Thank You for the work done on both Bitshares PPA and Debian.
Will surely delegate You as soon as I get this gui client working :)
In fact I have already sourced your ppa into my system.
But there is only cli tool and no GUI version to please my laziness.
(I believe there are many like me. I could have been using bitshares but since there is no ready-to-use tool I just don't).
I hope 'dacsunlimited' will recognize your fruitful efforts and agree to incorporate your auto-builders.
If they don't it will be a clear message that they are doing a sabotage on the project!
We are not doing a sabotage on the project, being surprised people are saying in this way. And confusing about where does these misunderstanding come from.
There is a lot of Linux distributions, as we announced before, we are not going to have Linux GUI Support currently, it is not our high priority. Most of the users working on Linux have the ability to built from source following the guide.
But we're very grateful for the work from maqifrnswa, the only thing left is to get the package verified and published I guess, I'm not familiar with PPA, please file an issue on https://github.com/dacsunlimited/bitsharesx/issues, and then we can discuss and get it done.
-
I directed DSL to this thread. Thanks maqifrnswa.
Thank you, Toast.
-
(..)See my PPA in my signature for packages. (..)
Dear mqifrnswa!
Could You please check on the quality of the most recent bitshares build for Ubuntu?
1. After launching the program it complains immediately:
JSON Parse error: Property name must be a string literal [show details]
2. In bottom right corner the connection indicator always shows 'Not connected'
This bug was closed by valzav with explenation that it is hard to replicate.
https://github.com/BitShares/web_wallet/issues/420
But I obtained same results on two separate machines:
a) Ubuntu 14.04.1 LTS
b) Ubuntu 14.10 (almost fresh install)
I installed win7 in virtual environment to check for comparison and windows version doesn't report these json parsing bugs.
My thought of the day is that before cluttering GitHub more with bug reports we could first check the build if it is compiled against correct libs, etc.
-
(..)See my PPA in my signature for packages. (..)
Dear mqifrnswa!
Could You please check on the quality of the most recent bitshares build for Ubuntu?
1. After launching the program it complains immediately:
JSON Parse error: Property name must be a string literal [show details]
2. In bottom right corner the connection indicator always shows 'Not connected'
This bug was closed by valzav with explenation that it is hard to replicate.
https://github.com/BitShares/web_wallet/issues/420
But I obtained same results on two separate machines:
a) Ubuntu 14.04.1 LTS
b) Ubuntu 14.10 (almost fresh install)
I installed win7 in virtual environment to check for comparison and windows version doesn't report these json parsing bugs.
My thought of the day is that before cluttering GitHub more with bug reports we could first check the build if it is compiled against correct libs, etc.
+5%
-
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 (https://bitsharestalk.org/index.php?topic=11237.0)
I'm starting to think that we might miss a dependency or something.
-
To me it seems the GUI (more precisely, the web_wallet) was not compiled properly
-
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.
-
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?
$ 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
-
One more thing, maybe try:
$ mv peers.leveldb peers.levedb.old
$ mkdir old
$ mv *.json old
and let the client rebuild them?
-
One more thing, maybe try:
$ mv peers.leveldb peers.levedb.old
$ mkdir old
$ mv *.json old
and let the client rebuild them?
$ 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..
-
amd64... that narrows it down, I've been testing on i386
thanks for your help hunting this down!
-
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.
sudo apt-get install virtualbox-guest-dkms (after restarting you will be able to increase screen resolution)
-
You might find more info in the browser console too..
-
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...
-
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.
-
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?
-
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
-
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.
-
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.