Quote from: dobbstowncr on April 02, 2019, 07:18:13 PM

Quote from: dobbscoin on April 02, 2019, 05:51:09 PM

Quote from: dobbstowncr on April 02, 2019, 04:44:38 PM

Anybody been able to successfully run the linux-qt wallet? If so, what distro and version are you using?

I've tried it on three different machines running Ubuntu 16.04, 18.04 & 18.10 and all have problems with libboost libraries. The all of the machines run other wallets (like bitcoin, litecoin and the original Dobbscoin) just fine.
The installed libboost libraries are 1.6.5 and 1.6.7 but Dobbscoin 2.0 is demanding 1.6.2.

i installed the requested 1.6.2 libraries on one machine, but it did not solve the problem.

You building your own or using the pre-compiled?

Hmmmmmmmmmmmmmmmmmmm let's seeee.
Distributor ID: Debian
Description: Debian GNU/Linux 9.8 (stretch)
Release: 9.8
Codename: stretch

Using: dpkg -s libboost-dev | grep 'Version'
Version: 1.62.0.1

Didn't realize I had old libboost, just followed the spitup from
How do I compile a wallet for Windows?
https://bitcointalk.org/index.php?topic=5122755.msg50263855#msg50263855

and from How do I compile a daemon for linux?
https://bitcointalk.org/index.php?topic=5122755.msg50260944#msg50260944

Is shit not backwards compatible in the libboost-world?
I'll upgrade if i can and see..

Mostly tried the pre-compiled, although I tried the build on the 18.04 machine without any success.

If I get a chance, I'll try Debian 9.8 in VirtualBox.

While using the Google, I found that this issue is fairly common for Linux crypto wallets. None of the suggested fixes have worked yet

I'll keep at it, as I want to support the project. I'm still mining BOB on Mining-Dutch.nl (with an AntRouter R-1 woohoo) where, believe it or not, it seems to have come back from the dead.

I compiled from source this morning on Mint 19.1 - works fine, mostly. seems to be having some issue syncing, however it does recognize my masternode properly, which the pre-built windows version seems to be a having a problem with.

One thing I notice on both the Windows and Linux versions is I have only the single, initial transaction of 10,000 SLACK, but it shows 20,000. 10,000 Locked, 10,000 available. That should not be happening