V12 Release

TanteStefana said:
I have this same problem on Ubuntu, since testing - as has someone else, but I never saw a post explaining why or what to do:

https://bitcointalk.org/index.php?topic=421615.msg12182210#msg12182210

I've been opening a terminal to execute dash-qt because of this. And this is not an issue with having the executable box checked in properties. It's simply not looking or acting like a double clickable executable. Did a setting get messed up? It's annoying not to be able to use it GUI style. This happens on my laptop and ubuntu box.

Since it's not just me, I'd appreciate the help, so I can help others, thanks.
Click to expand...

  1. Login via ssh.
  2. cd Desktop
  3. vi Dash-Wallet.desktop (or whatever text editor you are using)
  4. Insert the following lines:
    Code: 
    [Desktop Entry]
Icon=application-x-executable
Name=Dash-Wallet
Type=Application
Exec=/home/tante/bin/dash-qt
  5. Save it
  6. Make it executable: chmod +x Dash-Wallet.desktop (or, on the Desktop itself: right-click on the new icon, Properties -> Permissions-tab, check "Execute" checkbox)
  7. Double-click on the new icon "Dash-Wallet" which magically appeared on your Ubuntu desktop
The path after "Exec" should be YOUR path to dash-qt of course.

Enjoy :smile:
 
Last edited by a moderator:
Solarminer said:
Thanks SirHikmat. Now it works. I improved my update script with the && instead of a sleep.
wget https://www.dashpay.io/binaries/dash-0.12.0.47-linux64.tar.gz -O - | tar -xz && ./dash-cli stop
sleep 30
rm .dash/debug.log .dash/peers.dat .dash/mncache.dat
cp dash-0.12.0/bin/dashd ~/
cp dash-0.12.0/bin/dash-cli ~/
./dashd
sleep 25
./dash-cli getinfo
Click to expand...
nice. Yesterday, I made a suggestion (didn't tested it), but I guess you didn't see it, because I edited my initial post: http://pastebin.com/sb0BRvbv
 
My MN update script below:

./dash-cli stop
rm dashd -fr
rm dash-cli -fr
rm rm .dash/debug.log .dash/peers.dat .dash/mncache.dat -fr
wget https://www.dashpay.io/binaries/dash-0.12.0.47-linux64.tar.gz
tar zxvf dash-0.12.0.47-linux64.tar.gz
mv dash-0.12.0/bin/dashd .
mv dash-0.12.0/bin/dash-cli .
chmod +x ./dashd
chmod +x ./dash-cli
./dashd
sleep 25
./dash-cli getinfo

Similar to others. Seems to do the trick with the latest cli changes etc. :)
 
All updated. I didn't startmany my nodes since there was no protocol change, feels so dirty. I really don't want to lose my place in the queue, haven't been paid in almost 5 days. I guess this release is for nodes like mine since it addresses the payment queue. Thanks for the fix.
 
Walter said:
My MN update script below:
./dash-cli stop
rm dashd -fr
rm dash-cli -fr
rm rm .dash/debug.log .dash/peers.dat .dash/mncache.dat -fr
wget https://www.dashpay.io/binaries/dash-0.12.0.47-linux64.tar.gz
tar zxvf dash-0.12.0.47-linux64.tar.gz
mv dash-0.12.0/bin/dashd .
mv dash-0.12.0/bin/dash-cli .
chmod +x ./dashd
chmod +x ./dash-cli
./dashd
sleep 25
./dash-cli getinfo
Similar to others. Seems to do the trick with the latest cli changes etc. :)
Click to expand...

It works, didn't think about moving dashd/dash-cli instead of copying. Saves space but a little risky since you don't have a backup. I like to download before stopping the daemon so you are only down for a few seconds.
 
Solarminer said:
It works, didn't think about moving dashd/dash-cli instead of copying. Saves space but a little risky since you don't have a backup. I like to download before stopping the daemon so you are only down for a few seconds.
Click to expand...
If you guys want to optimize your scripts, you both can unpack only the two files dashd and dash-cli instead of all the stuff in the tar.
i.e.: tar xzf dash-0.12.0.47-linux64.tar.gz dash-0.12.0/bin/dashd

happy scripting :grin:
 
Solarminer said:
It works, didn't think about moving dashd/dash-cli instead of copying. Saves space but a little risky since you don't have a backup. I like to download before stopping the daemon so you are only down for a few seconds.
Click to expand...

True, used to do that but figured I leave the tarballs anyway though so if I do need to go back I just alter the script back one version number and run it again :smile: I only clean up the tarballs once a major release is done and stable.

sirhikmat: Not a bad suggestion! Will try that next time :smile:
 
Last edited by a moderator:
Anyone mixing Darksend on Mainnet? Darksend is much better in v.12. We can mix Dash straight from Masternode wallets.
I don't have a Mainnet Masternode wallet with mixed DS transactions yet but check out this Testnet screenshot:
https://dashtalk.org/threads/v12-testing-thread.5484/page-153#post-64198

So... Let's support the community and do some DS mixing! We need each other to do the mixing let's not forget...
The success of this coin needs everyone, especially users... if people don't use this coin, adoption is not going to happen. And there are users out there who are privacy eccentric who would like to anonymize their coins before using them.

Let's open our wallets and press that button "Start Darksend Mixing" !

Thanks, guys! :smile:
 
eduffield said:
Hmm, mine is showing a wrong address too. I smell a bug

./dash-cli masternode status
{
"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"pubKeyMasternode" : "XtdEd9b3yw2iEEfgjyQbwp82viVrwNE2sv",
"status" : "Not capable masternode: Could not find suitable coins!"
}
Click to expand...
pubKeyMasternode shows still wrong address.
 
Solarminer said:
What I want to do is download the .gz grab the dashd and dash-cli and put them in the home directory. Will this command do that? Or does it still leave the directory structure?
wget https://www.dashpay.io/binaries/dash-0.12.0.47-linux64.tar.gz -O - | tar -xzf dash-0.12.0/bin/dashd dash-0.12.0/bin/dash-cli
That didn't work. Getting closer. Should be something like this.
wget https://www.dashpay.io/binaries/dash-0.12.0.47-linux64.tar.gz -O - | tar -xz dash-0.12.0/bin/dashd -C ~/
Click to expand...

You'll still have the directory structure. If you don't want that, you have to use gnu-tar (installed anyway in most linux derivates). Then you can use:
Code: 
tar -zxf dash-0.12.0.47-linux64.tar.gz --no-anchored dashd --transform='s/.*\///'

Update: add "-C ~" for extracting into home directory
maybe we should discuss this in another thread...before we get kicked :confused:
 
Got it. This stops the daemon, downloads the dashd and dash-cli overwrites them with new versions without saving any other files. Need to run from the directory where the dashd and dash-cli files are stored.
./dash-cli stop
wget https://www.dashpay.io/binaries/dash-0.12.0.47-linux64.tar.gz -O - | tar -xz --overwrite --no-anchored dashd dash-cli --transform='s/.*\///'
rm .dash/debug.log .dash/peers.dat .dash/mncache.dat
./dashd && sleep 25 && ./dash-cli getinfo

Thanks for the help SirHikmat!
 
Last edited by a moderator:
Solarminer said:
I see .47 on Dashninja too. I am going to blame this on Tante. This quote Jinxed it.
Click to expand...

Ooops! My daughter days I hope way too much, makes me knock on wood. There is a piece of wood in my car just for the occasion, LOL.

SirHikmat said:
Your problem made me think. Well, I did some test on a ubuntu workstation today. It seems, that the file type is reported as a shared library which normally can't be executed and ubuntu notifying you about this.
Code: 
> file dash-qt
dash-qt: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=cb0c908c8ce1707866c5a5bbee24d1da2da97e62, stripped

The file manager of ubuntu check the file type and try to find an application to run it with. But why is it working on the shell? A shell just looks if the executable bit is set regardless of what type of file it is.

Solution: The devs have to "re"-add the correct file type.
Click to expand...

Thank you so much for the explanation! Hopefully eduffield saw this?

crowning said:
  1. Login via ssh.
  2. cd Desktop
  3. vi Dash-Wallet (or whatever text editor you are using)
  4. Insert the following lines:
    Code: 
    [Desktop Entry]
Icon=application-x-executable
Name=Dash-Wallet
Type=Application
Exec=/home/tante/bin/dash-qt
  5. Save it
  6. Double-click on the new icon "Dash-Wallet" which magically appeared on your Ubuntu desktop
The path after "Exec" should be YOUR path to dash-qt of course.

Enjoy :smile:
Click to expand...

Awesome, so glad I can set it right! Thanks!
 
You must log in or register to reply here.
Back
Top