Anyone tried out my " Most Secure, Least Hassle, Security Option"? Had problems installing Ubuntu? Problems booting from the DVD you burned? Have you read about changing the UEFI setup mentioned in this article and decided it's not worth the effort? Okay, maybe it's just a tad bit less secure, but an Ubuntu install inside a virtual machine is the next best thing to a standalone alongside Windows install, and I've updated the post to include that option (step 2a). I've also written up a VirtualBox install and initial configuration HOWTO for anyone who's up to the challenge. ;-) |
|
|
|
could someone clarify what stable release now, 0.9.2.12 or some later (found on git) ?
You can use either. 0.9.2.12 is the latest windows build, github is ahead with a non essential update at 0.9.2.13. Close and constant Dev contact is a good way to keep a coin alive. Glad to see your greater involvement. BTW, I lost some coins on Mintpal as well, but for privacy reasons, laziness, and also a desire to contribute, I'm not going to bother either of us with the matter (wouldn't mind knowing more about the technical specifics though). Cheers, and keep up the good work. |
|
|
|
My wallet is stuck at block 423911
and does not sync
I am running windows 8.1 and 8 weeks behind
Wallet is encrypted but I cannot unlock
any help
Make sure you have the digibyte.conf file installed in the same directory as your wallet.dat file. Upon installing, the program will probably automatically force you to reindex. You can find the contents of the digibyte.conf file on the OP. |
|
|
|
im trying to start solo mining with sha256 but in this step cant change it on properties, not accept be renamed ... say its not valid name for target
Create a shortcut of your DigiByte wallet, right click, click properties append --server to the end of the TARGET line
(Example: C:\Users\User\Wallets\DigiByte\digibyte-qt.exe --server)
Save it and run your DigiByte Wallet as a server using that newly created shortcut.
Right-click the shortcut icon of your wallet a. choose Properties b. click the Shortcut tab c. in the Target, add -server to the end. (Example: "C:\Program Files\DigiByte\digibyte-qt.exe" -server) |
|
|
|
Not sure what more I can do to help you mate. I don't know why your wallet is segfaulting but I'm fairly certain its due to your setup. I also run virtualbox and don't experience your problem but maybe you could try and compile another coin thats on the 0.9 codebase (e.g MyriadCoin) and see if you can run get their QT wallet running. If you can't then I'll do a fresh install of virtualbox to see if I can replicate your problem.
Remember, the "prefab" digibyte-qt downloadable from www.digibyte.co in the ZIP file at http://www.digibyte.co/sites/digibyte.co/files/DigiByte-3.0.3-ubuntu-64bit.zip DOES NOT GENERATE THESE SAME ERRORS when run on the same system with no modifications. That means that it is highly unlikely to be a VituralBox issue, and is rather an issue limited to this particular compile itself. If you can do a fresh install and some of your own testing to match, that would be great. I've got another VirtualBox install where I'm going to test as well. On the other hand, I share your frustration and can understand if you have more important things to do. I'm not going to spend my entire Easter Weekend compiling a DGB wallet either! Next week it's back to work, and like it or not, I won't have time to "play" until summer. The prefab Digibyte-qt works better (or just as well anyway, and with a lot less effort) than the version I compiled, which works fine after generating the initialization errors by the way, so perhaps we might just leave things as they are until someone more appropriate, like someone on DigiByte "permanent staff", addresses the need to improve the Ubuntu DigiByte-qt. I thought this might be something doable and fun for the hobbyist, but I've been proven wrong. Time to make due with what we've got and wait until the Devs give us something better, more than anything, because I'm out of time. Thanks for your helping hand. I was fun and I learned a lot! Tested against digibyte-master on another Ubuntu installation with the same results. Just a bunch of annoying errors in Terminal on startup. libprotoc-dev is not necessary BTW. Going to finish up by timing the complete sync time of this 'custom' compile, and then call it a day. Thanks again. |
|
|
|
Not sure what more I can do to help you mate. I don't know why your wallet is segfaulting but I'm fairly certain its due to your setup. I also run virtualbox and don't experience your problem but maybe you could try and compile another coin thats on the 0.9 codebase (e.g MyriadCoin) and see if you can run get their QT wallet running. If you can't then I'll do a fresh install of virtualbox to see if I can replicate your problem.
Remember, the "prefab" digibyte-qt downloadable from www.digibyte.co in the ZIP file at http://www.digibyte.co/sites/digibyte.co/files/DigiByte-3.0.3-ubuntu-64bit.zip DOES NOT GENERATE THESE SAME ERRORS when run on the same system with no modifications. That means that it is highly unlikely to be a VituralBox issue, and is rather an issue limited to this particular compile itself. If you can do a fresh install and some of your own testing to match, that would be great. I've got another VirtualBox install where I'm going to test as well. On the other hand, I share your frustration and can understand if you have more important things to do. I'm not going to spend my entire Easter Weekend compiling a DGB wallet either! Next week it's back to work, and like it or not, I won't have time to "play" again until next summer. The prefab Digibyte-qt works better (or just as well anyway, and with a lot less effort) than the version I compiled, which works fine after generating the initialization errors by the way, so perhaps we might just leave things as they are until someone more appropriate, like someone on DigiByte "permanent staff", addresses the need to improve the Ubuntu DigiByte-qt. I thought this might be something doable and fun for the hobbyist, but I've been proven wrong. Time to make due with what we've got and wait until the Devs give us something better, more than anything, because I'm out of time. Thanks for your helping hand. I was fun and I learned a lot! |
|
|
|
i have 1 gridseed about 10ghash i put yesterday to mine DigiByte in p2p http://digihash.co/ , but really give small rewards of 4 coins, can make solo mining with this miner better that join to pool? You could try it in scrypt mode to see if you get any better results with that pool instead, but one gridseed isn't going to generate very much at all. Like your avatar bud! |
|
|
|
Yep you are missing the dependencies required to make the QT. Try the following sudo apt-get install libminiupnpc-dev libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev libqrencode-dev
then run ./configure and make again. Make created a good shared library file (found in digibyte/src/qt) that only runs from the command prompt and that generates the following warnings and errors: OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
Segmentation fault (core dumped)
Shouldn't we end up with an executable? Add: it looks like the generic build on digibyte.co is actually better than this, as horrible as it is . . . This looks more like an OpenGL virtualbox problem rather than a wallet problem. Do you have 3d acceleration enabled in virtualbox? Did you install video card drivers or the virtualbox tools? I agree. I do have 3d acceleration enabled, did not install any special video drivers, and am using the default virtualbox install drivers. ADD: I posted that original post in a rush before dinner, and, now, after doing a quick search . . . https://www.virtualbox.org/ticket/12941?cversion=0&cnum_hist=72ADD 2: Kind of looks like it's the end of the road for this on VirtualBox . . . as long as it's got 3D elements anyway. This looks like it might be an unresolved VirtualBox issue. VirtualBox compatibility is very important I think. Perhaps it might be a good idea to strip the Linux wallet of 3D? ADD 3: Very interesting to note that the "prefab" digibyte-qt downloadable from www.digibyte.co in the ZIP file at http://www.digibyte.co/sites/digibyte.co/files/DigiByte-3.0.3-ubuntu-64bit.zip DOES NOT GENERATE THESE SAME ERRORS when run on the same system with no modifications. NOT a VituralBox issue. |
|
|
|
Yep you are missing the dependencies required to make the QT. Try the following sudo apt-get install libminiupnpc-dev libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev libqrencode-dev
then run ./configure and make again. Make created a good shared library file (found in digibyte/src/qt) that only runs from the command prompt and that generates the following warnings and errors: OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0x7f243e775ad0
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0x7f243e775ad0, failed to get XVisualInfo
Segmentation fault (core dumped)
Shouldn't we end up with an executable? Add: it looks like the generic build on digibyte.co is actually better than this, as horrible as it is . . . |
|
|
|
Yep you are missing the dependencies required to make the QT. Try the following sudo apt-get install libminiupnpc-dev libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev libqrencode-dev
then run ./configure and make again. I think I've got it. I've added libprotoc-dev, libprotobuf-dev, and protobuf-compiler to the list (libprotoc-dev might not be necessary though, I'll have to check that later), and I've got a good config done. Doing another make. It takes time, but I'll let you know when I've got some news. |
|
|
|
Lol, get Sudo-idontunderstand-apt  /Gofigure Wow, you are on top of things! Is the avatar upload an Easter present, or is it back for good? Whatever the case, better make hay while you can. |
|
|
|
Yep you are missing the dependencies required to make the QT. Try the following sudo apt-get install libminiupnpc-dev libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev libqrencode-dev
then run ./configure and make again. configure: WARNING: PROTOC not found; bitcoin-qt frontend will not be built |
|
|
|
Yep you are missing the dependencies required to make the QT. Try the following sudo apt-get install libminiupnpc-dev libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev libqrencode-dev
then run ./configure and make again. I'm on it. Third time's a charm. Add: looks like that was partially my mistake as well - appreciate your help! |
|
|
|
sudo apt-get install libdb4.8-dev Error: Package 'libdb4.8-dev' has no installation candidate You are missing dependencies. Try the following steps in full. This step will get you access to the above libdb4.8-dev package on Ubuntu. sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update If you are instead on Debian then the process is a little different you want to edit your sources.list and add the line beginning with deb to the bottom of the file replacing [mirror] with your closest debian mirror (you can copy from the urls already in this file, the important part is the "oldstable main" part). Make sure to apt-get update after adding the line! nano /etc/apt/sources.list
deb http://[mirror]/debian/ oldstable main
sudo apt-get update Next we download and all install all the required dependences. Note that if you are on Debian you may need to change the package "libboost1.54-all-dev" to "libboost1.49-all-dev". sudo apt-get install build-essential libtool autotools-dev autoconf libssl-dev libboost-all-dev libdb4.8-dev libdb4.8++-dev libboost1.54-all-dev libminiupnpc-dev libqt5gui5 libqt5core5 libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev libqrencode-dev git nano Now we clone the source code for digibyte and move into that directory git clone https://github.com/digibyte/digibyte
cd digibyte Now we can compile the source code into the Daemon (digibyted) and the GUI Wallet (Digibyte-Qt). ./autogen.sh
./configure
make If you now check the src folder you will have digibyted and digibyte-Qt. We're making progress, but it’s still a no go. At the end of the process, there’s no digibyte-qt to be found anywhere. Here are the step-by-steps I took on a new Ubuntu 14.04 install (with errors commented): sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install build-essential libtool autotools-dev autoconf libssl-dev libboost-all-dev libdb4.8-dev libdb4.8++-dev libboost1 ERROR: Unable to locate package libboost1 (I eliminated that from the command and proceded.) git clone https://github.com/digibyte/digibyteOn a new install, you get “The program 'git' is currently not installed. You can install it by typing: sudo apt-get install git”. Obviously, that is self-explanatory, and all you need to do is follow the instructions, and then repeat the git clone command.sudo apt-get install git git clone https://github.com/digibyte/digibytecd digibyte ./autogen.sh ./configure ERROR (from config.log): WARNING: libprotobuf not found; bitcoin-qt frontend will not be builtmake digibyted is in ~/src, but there is no digibyte-Qt to be found anywhere. |
|
|
|
The direct link is a good idea, and I do understand everybody else's needs. However, does DigiByte really need third party download sites (not to mention third party download sites linked to pirated software)? Think of the negative PR that comes from that! (Both conscious and subconscious.) Don't we have www.digibyte.co and github that, between the two, can take care of all of our needs? I agree with you here and its why I suggested that Jared add a "Full Install" for the digibyte wallet. But you need to understand that bandwidth costs money and the current bootstrap.dat is 800MB. Often times when you buy a website hosting plan it comes with a limited amount of bandwidth and if you are hosting large files that people are downloading regularly you can quite often run over that limit. Whereas putting bootstrap.dat on a public tracker costs us nothing at all and it will be available for a long time to come! It's also worth noting that the official Bitcoin website doesnt host its own copy of the blockchain (or bootstrap.dat) for the above reasons. I and the Digibyte Team are in no way related to Kickass.to or any other torrent tracker and I was simply using it as a means to an end. The main thing to take away from this is that we are aware that the initial sync time can easily become a problem and are actively working towards solving that problem! 24hralttrade - This was the initial idea behind DigibyteWiki.com and I'd love to see you guys help me out with articles and downloads if you PM me your idea's I'm sure we can make it happen! Another idea is to just sync. What with zero, or next to zero, peers and seeds, the torrent will probably even take longer (I say "probably" tongue-in-cheek since I still haven't been able to download it). This on top of giving a very bad impression! Hey, tell folks that transfer speed is what THEIR "end-of-the-loop" transfer speed is, and leave it at that. |
|
|
|
Somebody bought on 30 sat 2015-04-02 14:14:34 Buy 0.00000030 2338.48453189 0.00070155 Lucky bastard Never happened. Bad data. |
|
|
|
We need something  @HR CAN WE USE YOURE FORUM!?!  Yes it's a little manic here right now. What with DigiByte popping in with stuff on the translations as well, I thought that maybe I'd missed something important. Unfortunately, when going back and reading, I found I was wrong.  That's okay with me though. I'm a long term, slow but sure kind of guy who's happy to plug away at the nuts and bolts. Back to the Ubuntu wallet . . . Is it a yes ugh?  I really want to keep Asistec-TI on topic, and since that's pretty much centered on the educational - explaining the technical and demonstrating how - I don't see much room there for causal conversation. I gave the idea of creating a separate sub-forum in 'General and Admin', maybe with the name of 'The Bar', some thought, but it's just too much work and I don't have the time to monitor something busy. Sorry, but I've got to stick with the main purpose and guidelines I've set for the forum. Hey, that doesn't mean you're not welcomed though. Anytime anyone wants to post something useful (and that could be something as seemingly simple and insignificant as a failed attempt to do something coupled with a question) whose aim is to better explain and make easier, the board's all yours! (Please just don't be put off by the security measures you've got to jump through - it was getting attacked pretty hard - after the first few posts you'll be on the inside looking out.) |
|
|
|
|
~/DigiByteProject$ automake
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
configure.ac:691: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
ADD:
~/DigiByteProject$ make -f Makefile.in
Makefile.in:15: *** missing separator. Stop.
|
|
|
|
|
Show Posts
