|
bitcreditscc (OP)
|
 |
May 03, 2015, 05:33:14 PM |
|
maybe we need to redownload the chain? just a thought.
no, it's a QT related issue, i'm looking into it. Meanwhile, just use the daemon i included in the release. linux users and service providers are all using the update with no problem. I'll work on it tonight and figure out whats wrong. |
|
|
|
Department of
Member
 Offline
Activity: 102
Merit: 10
|
|
May 03, 2015, 06:16:26 PM |
|
Hey, whoever said they could donate to get the new logo, you can send however much you want to this Bitcoin address: 18t5BpvRMsLaCDdLtpwSFDrA4xa8jLF95x I'm going to go back to the guy who made this one and get a few variations of it, change colors, wording (to Blockchain Banking), etc and get all the files and things we might need. Let me know about any final suggestions or feedback you might have.  |
|
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 12:10:43 AM |
|
A backtrace came up with this :- (gdb) backtrace
#0 WalletModel::getOptionsModel (this=0x0) at qt/walletmodel.cpp:413
#1 0x0000555555709a7c in OverviewPage::darkSendStatus (this=0x555556cba8e0) at qt/overviewpage.cpp:390
#2 0x000055555574a588 in OverviewPage::qt_static_metacall (_o=0x555556cba8e0, _id=1, _a=0x7fffffffc8d0, _c=<optimized out>) at qt/moc_overviewpage.cpp:68
#3 0x00007ffff5f61a7a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4 0x00007ffff5f65e0b in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5 0x00007ffff6a4411c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#6 0x00007ffff6a4a870 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7 0x00007ffff5f4d86d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8 0x00007ffff5f7d4eb in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9 0x00007ffff5f7a711 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007ffff339cc5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff339cf48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff339cffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff5f7b031 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x00007ffff6ae74e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x00007ffff5f51411 in QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#16 0x0000555555725377 in SendCoinsDialog::addEntry (this=this@entry=0x5555573b20c0) at qt/sendcoinsdialog.cpp:404
#17 0x000055555572548a in SendCoinsDialog::SendCoinsDialog (this=0x5555573b20c0, parent=<optimized out>) at qt/sendcoinsdialog.cpp:45
#18 0x0000555555677181 in WalletView::WalletView (this=0x555556cba020, parent=<optimized out>) at qt/walletview.cpp:71
#19 0x0000555555662a4d in WalletFrame::addWallet (this=0x555556b7f150, name=..., walletModel=0x555556e72710) at qt/walletframe.cpp:45
#20 0x00005555555e57a8 in BitcreditApplication::initializeResult (this=0x7fffffffde00, retval=<optimized out>) at qt/bitcredit.cpp:427
#21 0x00005555555e5c1f in BitcreditApplication::qt_static_metacall (_o=0x7fffffffde00, _id=<optimized out>, _a=0x7fffd3820310, _c=<optimized out>) at qt/bitcredit.moc:169
#22 0x00007ffff5f65f41 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x00007ffff6a49203 in QApplication::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#24 0x00007ffff6a4411c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x00007ffff6a4a870 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#26 0x00007ffff5f4d86d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x00007ffff5f50f41 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x00007ffff5f7aed3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#29 0x00007ffff339cc5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007ffff339cf48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007ffff339cffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007ffff5f7b031 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x00007ffff6ae74e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#34 0x00007ffff5f4c4f1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#35 0x00007ffff5f4c805 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#36 0x00007ffff5f51f67 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#37 0x00005555555d1c85 in main (argc=1, argv=<optimized out>) at qt/bitcredit.cpp:630
very weird |
|
|
|
gjhiggins
Legendary
Offline
Activity: 2254
Merit: 1278
|
|
May 04, 2015, 12:39:42 AM |
|
no, it's a QT related issue, i'm looking into it
Compiled under Ubuntu 14.04, the GUI ran successfully once but segfaulted thereafter until datadir is zeroed, compiled daemon works fine. Eventually I managed to get the GUI to stay up by specifying -litemode=1. I guess that disables the problematic bit. Cheers Graham |
|
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 01:25:00 AM |
|
no, it's a QT related issue, i'm looking into it
Compiled under Ubuntu 14.04, the GUI ran successfully once but segfaulted thereafter until datadir is zeroed, compiled daemon works fine. Eventually I managed to get the GUI to stay up by specifying -litemode=1. I guess that disables the problematic bit. Cheers Graham confirmed can you run backtrace on your system and see if you get similar results? |
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 01:25:30 AM |
|
so everyone just add litemode=1 in your config for now.
|
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 03:28:12 AM |
|
diff adjustment working well enough, large sudden drop in hash.
|
|
|
|
|
|
|
starblocks
|
|
May 04, 2015, 11:08:59 AM |
|
that blog post is not so well written lol as i'm no writer
get on skype
just did and shared a few marketing ideas for when you get them - probably all obvious stuff but thought i would in case any of them hadn't been considered yet |
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 06:55:31 PM |
|
So there is a proposal by one of the new guys, basically, he wants us to release 230K fro the 6 mill fund. This will be placed in a faucet that will give out 23 BCR. This will be a means to reach out to new users alongside a massive marketing campaign.
Thoughts?
|
|
|
|
dbt1033
Legendary
Offline
Activity: 1274
Merit: 1000
|
|
May 04, 2015, 07:08:32 PM |
|
So there is a proposal by one of the new guys, basically, he wants us to release 230K fro the 6 mill fund. This will be placed in a faucet that will give out 23 BCR. This will be a means to reach out to new users alongside a massive marketing campaign.
Thoughts?
I think that would be an excellent idea...as long as the faucet monitors IP addresses  |
|
|
|
|
|
alganonim
|
|
May 04, 2015, 07:58:48 PM |
|
So there is a proposal by one of the new guys, basically, he wants us to release 230K fro the 6 mill fund. This will be placed in a faucet that will give out 23 BCR. This will be a means to reach out to new users alongside a massive marketing campaign.
Thoughts?
I think that would be an excellent idea...as long as the faucet monitors IP addresses Great idea, indeed it should be inspected in some way, linked with bitcointalk account ? , but then not anonymous. But such promotional action should be made in some "stable time" not like now when wallet problems occour and price dumps, so this steps should be carefully planned, new versions will bring new functions and high expectations but also probability of failure. Something should be done to add BCR to at least one more exchange, no one expects cryptsy right now, but c-cex should be enough to decentralise market. One wallet maintenance could start a panic and we are gone. |
|
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 04, 2015, 09:06:19 PM |
|
Can't start banknode on my VPS with the new daemon.
./bitcredit-cli banknode start
you must set banknode=1 in the configuration
Yes, I have changed masternode=1 to banknode=1 (and tried changing masternodeprivkey and masternodeaddr lines to bankprivkey and bankaddr)
|
|
|
|
|
|
alganonim
|
|
May 04, 2015, 09:29:58 PM |
|
Can't start banknode on my VPS with the new daemon.
./bitcredit-cli banknode start
you must set banknode=1 in the configuration
Yes, I have changed masternode=1 to banknode=1 (and tried changing masternodeprivkey and masternodeaddr lines to bankprivkey and bankaddr)
masternodeprivkey and masternodeaddr lines to banknodeprivkey and banknodeaddr |
|
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 09:31:21 PM |
|
Can't start banknode on my VPS with the new daemon.
./bitcredit-cli banknode start
you must set banknode=1 in the configuration
Yes, I have changed masternode=1 to banknode=1 (and tried changing masternodeprivkey and masternodeaddr lines to bankprivkey and bankaddr)
banknodeprivkey and banknodeaddrdouble and triple check. and if it's a daemon with a BN, don't use 'litemode" |
|
|
|
fishbone
Member
Offline
Activity: 89
Merit: 10
|
|
May 04, 2015, 10:18:34 PM |
|
Faucet sounds like a good idea  |
|
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 04, 2015, 10:33:21 PM
Last edit: May 04, 2015, 10:52:28 PM by thelonecrouton |
|
Can't start banknode on my VPS with the new daemon.
./bitcredit-cli banknode start
you must set banknode=1 in the configuration
Yes, I have changed masternode=1 to banknode=1 (and tried changing masternodeprivkey and masternodeaddr lines to bankprivkey and bankaddr)
banknodeprivkey and banknodeaddrdouble and triple check. and if it's a daemon with a BN, don't use 'litemode" Yep, sorry, banknodeprivkey and banknodeaddr are what I meant. Not working. Not using litemode, whatever that is. Do I need to generate a new banknodeprivkey? edit: generating a new banknodeprivkey did it. |
|
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 10:47:47 PM |
|
Can't start banknode on my VPS with the new daemon.
./bitcredit-cli banknode start
you must set banknode=1 in the configuration
Yes, I have changed masternode=1 to banknode=1 (and tried changing masternodeprivkey and masternodeaddr lines to bankprivkey and bankaddr)
banknodeprivkey and banknodeaddrdouble and triple check. and if it's a daemon with a BN, don't use 'litemode" Yep, sorry, banknodeprivkey and banknodeaddr are what I meant. Not working. Not using litemode, whatever that is. Do I need to generate a new banknodeprivkey? no, my nodes are up and running. wait are you running a cold or hot node? |
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 11:16:50 PM |
|
Maybe those gifted with graphics can pick this up and make it professional? |
|
|
|
|
bitcreditscc (OP)
|
|
May 04, 2015, 11:57:06 PM |
|
Don't mind me, i just happen to have time. |
|
|
|
|
