Bitcoin Forum
December 11, 2016, 04:11:16 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1] 2 »  All
  Print  
Author Topic: Please help test: version 0.5 release candidate 1  (Read 5590 times)
Gavin Andresen
Legendary
*
qt
Offline Offline

Activity: 1652


Chief Scientist


View Profile WWW
October 10, 2011, 04:09:36 PM
 #1

I just tagged the git tree "v0.5.0rc1". If you are able, please compile and help test.

See the INSTALL file at the top of the source tree for instructions on compiling. Binary releases for at least unix and mac should be available in the next day or two (there is a show-stopper bug on Windows, and we could use help from people familiar with cross-compiling using mingw to update the Windows build process).

Major bugs you should be aware of:

Wallet does not relock on Win32

Major changes from version 0.4:

Switched from wxWidgets for the GUI to Qt, using Wladimir J. van der Laan's bitcoin-qt. Why? We didn't have any wxWidgets programmers contributing fixes or improvements.

New JSON-RPC commands:

getmemorypool : alternative to 'getwork' that provides everything needed to construct a block with a custom generation transaction.
listsinceblock : Get all transactions in blocks since block [blockid]
signmessage/verifymessage : sign/verify a message with a wallet public/private keypair

Deprecated JSON-RPC features:
'midstate' data item from getwork requests

Deprecated JSON-RPC commands that have been REMOVED:
setlabel
getlabel
getaddressesbylabel
getamountreceived
getallreceived
getreceivedbylabel
listreceivedbylabel

Run: git shortlog --no-merges v0.4.0..
... to get a complete list of changes, and thanks to everybody who is contributing!


How often do you get the chance to work on a potentially world-changing project?
1481429476
Hero Member
*
Offline Offline

Posts: 1481429476

View Profile Personal Message (Offline)

Ignore
1481429476
Reply with quote  #2

1481429476
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481429476
Hero Member
*
Offline Offline

Posts: 1481429476

View Profile Personal Message (Offline)

Ignore
1481429476
Reply with quote  #2

1481429476
Report to moderator
jimrandomh
Jr. Member
*
Offline Offline

Activity: 43


View Profile
October 10, 2011, 08:18:13 PM
 #2

Thanks for all your hard work! But does this being a release candidate mean that multi-sigs/receiver-scripts won't be available on testnet until 0.6 or later?
Gavin Andresen
Legendary
*
qt
Offline Offline

Activity: 1652


Chief Scientist


View Profile WWW
October 10, 2011, 08:39:56 PM
 #3

Thanks for all your hard work! But does this being a release candidate mean that multi-sigs/receiver-scripts won't be available on testnet until 0.6 or later?

Hmm?  testnet accepts non-standard transactions today (I've been doing some experiments with multi-sig transactions on the testnet).

How often do you get the chance to work on a potentially world-changing project?
AlexWaters
Member
**
Offline Offline

Activity: 72


Coin.co | Twitter:@watersNYC


View Profile
October 10, 2011, 10:36:30 PM
 #4

I am having trouble building in windows, see https://github.com/bitcoin/bitcoin/issues/581

On top of the winx64 build issue -
One of my long-term goals would be to have Jenkins churn out stand-alone bitcoin.exe - they wouldn't need any dependencies and work in windows x86 and x64. (Similar to the win32-setup.exe at http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/). I believe if we make this process really automated and fluid, more people will be able to test faster.

Matt has been very helpful with getting Jenkins to pull from my testing repo, and the builds are working well in Ubuntu. QT is much faster in my limited testing, and just feels better overall. Kudos to Wladimir and the others who contributed.


ripper234
Legendary
*
Offline Offline

Activity: 1260


Ron Gross


View Profile WWW
October 11, 2011, 12:56:07 PM
 #5

I just tagged the git tree "v0.5.0rc1". If you are able, please compile and help test.

See the INSTALL file at the top of the source tree for instructions on compiling. Binary releases for at least unix and mac should be available in the next day or two (there is a show-stopper bug on Windows, and we could use help from people familiar with cross-compiling using mingw to update the Windows build process).

Major bugs you should be aware of:

Wallet does not relock on Win32

Major changes from version 0.4:

...


Good work!

Could you post/link to a list of major features? I know there are more than what you just wrote above.
E.g. (assuming LiteCoin client = Bitcoin Client), the client I just downloaded a few days ago has an awesome progress bar to show how much time is needed to download the full blockchain. I can also see some more data on the blocks I mined, like when they're expected to be available in my balance. Is there anything more? (Or perhaps this was just a feature of 0.4 that I missed? I skipped that version)

Also - I found something that looks like a bug with the LiteCoin version I downloaded, and I suspect it originates from Bitcoin and was not introduced in LiteCoin. I described it here:

Quote
1. I mined my first two blocks.
2. Tried to transfer 10 LTC to my own address.
3. Failed because of not enough confirmation "Mined balanced will be available in 118 blocks"
4. Now, the bug: I see 3 as Number of Transactions in the overview tab, but I actually have only the 2 solved blocks.
5. This persisted even after a restart of the client ...
6. Another restart - now I see 4 as Number of Transactions, still only 2 actual transactions.

Where did the 3rd transaction come from? Is it a Bitcoin or LiteCoin bug? Should I report this on Bitcoin github?

Please do not pm me, use ron@bitcoin.org.il instead
Mastercoin Executive Director
Co-founder of the Israeli Bitcoin Association
Luke-Jr
Legendary
*
expert
Offline Offline

Activity: 2100



View Profile
October 13, 2011, 11:28:38 PM
 #6

Not sure what trouble BlueMatt et al are having, but I managed to build some Windows binaries. No guarantees, backup your wallet, etc...

Also, note that these aren't technically 0.5.0rc1, because I built with the very minor makefile changes made afterward (commits a1e0bb5a and e44a00ae) as well as having to hack up the build files more to make it work with my mingw setup (Gentoo crossdev i686-pc-mingw w/ GCC 4.4).

I didn't bother to build with UPnP support either cuz I was too lazy to cross-compile miniupnp (and I just needed the signmessage functionality).


kwaaak
Full Member
***
Offline Offline

Activity: 139


View Profile
October 14, 2011, 09:28:57 PM
 #7

Built on Mac OS X 10.7.2

Code:
bitcoind/src/bitcoind: Mach-O executable i386

http://www.mediafire.com/?k690nwp8n661p7h
justusranvier
Legendary
*
Offline Offline

Activity: 1400



View Profile WWW
October 14, 2011, 10:36:35 PM
 #8

Everything seems to work well except than when I have "Minimize to the tray instead of the taskbar" enabled clicking on the close button doesn't do anything.
Bitsky
Hero Member
*****
Offline Offline

Activity: 542


View Profile
October 15, 2011, 09:04:30 AM
 #9

Not sure what trouble BlueMatt et al are having, but I managed to build some Windows binaries. No guarantees, backup your wallet, etc...

Also, note that these aren't technically 0.5.0rc1, because I built with the very minor makefile changes made afterward (commits a1e0bb5a and e44a00ae) as well as having to hack up the build files more to make it work with my mingw setup (Gentoo crossdev i686-pc-mingw w/ GCC 4.4).

I didn't bother to build with UPnP support either cuz I was too lazy to cross-compile miniupnp (and I just needed the signmessage functionality).


I've tested the two QT binaries on Win2k. They start perfectly fine Smiley
I used my real wallet.dat only with the network disabled (no offense at all, but I'll only use it with an official release). Seems there are no issues so far.
Thumbs up from me.

Bounty: Earn up to 68.7 BTC
Like my post? Feel free to drop a tip to 1BitskyZbfR4irjyXDaGAM2wYKQknwX36Y
Luke-Jr
Legendary
*
expert
Offline Offline

Activity: 2100



View Profile
October 15, 2011, 04:38:08 PM
 #10

FWIW, I am seeing reports (both my Windows binaries and also people building their own Ubuntu binaries) of 0.5.0rc1 corrupting wallets (both old and newly-made)!

Gavin Andresen
Legendary
*
qt
Offline Offline

Activity: 1652


Chief Scientist


View Profile WWW
October 15, 2011, 07:08:44 PM
 #11

Corrupting how? Did they install 0.5 and then downgrade (is it a backwards-compatibility issue)?
Did it get corrupted when they encrypted?
Anything interesting in their debug.log?

How often do you get the chance to work on a potentially world-changing project?
netrin
Sr. Member
****
Offline Offline

Activity: 322


FirstBits: 168Bc


View Profile
October 16, 2011, 02:00:24 AM
 #12

Hey Gavin et al,

Congratulations with this RC1. My comments are mostly superficial as the plumbing seems to 'just work'. With Qt, this is the first time I've successfully compiled from HEAD for months. That's a huge bonus in my world.

The incoming transaction notifications are subtle but informative. The client looks nice and lays out well full screen in xmonad 1280x800. UX failure begins in width <570px and height <226px; It needs scrollbars in small windows. Ambiguous dates (xx/xx/year) are unacceptable in an international product without localization, otherwise ISO 8601 (YYYY-MM-DD HH:mm:ss) UTC should be used.

The splash-screen wallet is cute but annoying. It does not play nice with my window manager. I can't hide it, move it, nor redirect it to another workspace. So I've got this box blocking whatever I'm doing for several seconds dead center screen.

I can guess, but not sure what the three icons indicate in the bottom right of the client; They could use some hover tool tips. mBTC and μBTC are clever if not hopeful as kBTC would be more realistic today Smiley. The dynamic 'clock' unconfirmed and 'check' status are perfectly informative. I can not see the sending address in my transaction history when receiving (from unknown?). Address book, meh.

In the future, I would like to see options such as import/export and more control/visibility of transactions, even if these features are deactivated by default.

The message "This transaction is over the size limit.  You can still send it for a fee of 0.0005 BTC, which goes to the nodes that process your transaction and helps to support the network.  Do you want to pay the fee?" is confusing, particularly if/when the user is sending a small amount (to him value IS the transaction). I would recommend "The network is congested" or really get into the sum(value * confirmations)/(bytes) with a "help"/"more info" link.

Aside from the fact that this is confusing, it's annoying that the user has no recourse, this 'feature' makes micro-payments less realistic. I would much prefer the message warned me that miners may decide not to send such a measly amount of money without paying a fee. Would I like to send it anyway YES or no? Bitcoin is a FREE market experiment after all. A suggested transaction with vague/estimated delays might be appropriate.

If the client asks for a passphrase on send, there is no need to also ask if he really intends to send coins. For small transactions, the user is unnecessarily replying yes three times before sending a coin.

IFF the client must ask me if I want to send a measly amount of money to which I may decline paying a fee and thus abort, it would be better to ask for the passphrase after I've fully confirmed my intention to send (including any fees) or at the same time.

Aside from my stalled micro-transaction (Smiley Thank Satoshi for main.h Smiley), everything looks and works very well! Thanks again for your hard work to produce a great client,
Netrin

Greenlandic tupilak. Hand carved, traditional cursed bone figures. Sorry, polar bear, walrus and human remains not available for export.
tvbcof
Legendary
*
Offline Offline

Activity: 1988


View Profile
October 17, 2011, 06:45:20 PM
 #13

I finally got around to re-compiling on my FreeBSD system last night off of Trunk (I think Smiley   I did it in part because I wanted to be sure I could re-compile in a hurry if need be.  Binary seems to work, though I have not tried to transfer any BTC with it.

Seems that I had to include some extra system header files in protocol.cpp for AF_INET and some other symbol.  I don't have the details in front of me, and I cannot say for sure that this was the fix or that I did it correctly, but after doing this I got a binary that appears to have download the blockchain as I slept and be processing transactions.  Didn't even try the tests.  I might be inclined to do so if someone takes enough of an interest in this platform to support it more cleanly.

finway
Hero Member
*****
Offline Offline

Activity: 714


View Profile
October 18, 2011, 07:52:00 AM
 #14

Under Windows 7 32bit :
The percentage showing is wrong,
when i close it and reopen it to continue downloading blocks,
it shows the wrong percentage number.

Synchronizing with network...             8%

"Catching up ...
Downloaded 32076 of 149724 blocks of transaction history.
Last received block was generated 658 day(s) ago."


ShadowOfHarbringer
Legendary
*
Offline Offline

Activity: 1470


Bringing Legendary Har® to you since 1952


View Profile
October 23, 2011, 08:30:03 PM
 #15

@Gavin

Any chance for including this in 0.5.x ?

https://github.com/bitcoin/bitcoin/pull/570

dooglus
Legendary
*
Offline Offline

Activity: 2002



View Profile
October 24, 2011, 07:47:15 PM
 #16

I built bitcoin-qt v0.5.0rc1 in Ubuntu 11.10 with the following packages installed and had the following problems.
Code:
||/ Name                      Version                   Description
+++-=========================-=========================-==================================================================
ii  build-essential           11.5ubuntu1               Informational list of build-essential packages
ii  libboost-dev              1.46.1.1                  Boost C++ Libraries development files (default version)
ii  libboost-filesystem-dev   1.46.1.1                  filesystem operations in C++ (default version)
ii  libboost-program-options- 1.46.1.1                  program options library for C++ (default version)
ii  libboost-system-dev       1.46.1.1                  Operating system (e.g. diagnostics support) library (default versi
ii  libboost-thread-dev       1.46.1.1                  portable C++ multi-threading (default version)
ii  libdb5.1++-dev            5.1.25-11                 Berkeley v5.1 Database Libraries for C++ [development]
ii  libqt4-dev                4:4.7.4-0ubuntu8          Qt 4 development files
ii  libssl-dev                1.0.0e-2ubuntu4           SSL development libraries, header files and documentation
ii  qt4-qmake                 4:4.7.4-0ubuntu8          Qt 4 qmake Makefile generator tool
  • doc/readme-qt.rst says that 'libdb4.8++-dev' is required, but it doesn't exist in the current version of ubuntu (oneiric).  Only one version exists, which is what I installed.  This debian bug talks about the issue.
Code:
chris@chris:~/Programs/bitcoin$ apt-cache search 'libdb[0-9].*\+\+-dev'
libdb5.1++-dev - Berkeley v5.1 Database Libraries for C++ [development]
  • In the 'Send coins' tab, hovering over the address book icon pops up a tooltip saying "Choose adress [...].  "Adress" is missing a 'd'.
  • In the same tab, clicking the address book icon opens a new window which has an 'ok' button but no 'cancel' button.
  • bitcoin-qt is very noisy on standard output.  Starting and just clicking through the 6 tabs along the top generates more than 3000 lines of text in the terminal that ran it.  Could these messages go to the debug.log file if they're needed?  Here's how it starts (piped through 'uniq -c' to remove duplicate lines):
Code:
chris@chris:~$ ~/Programs/bitcoin/bitcoin-qt | uniq -c
      1 Connected to accessibility bus at:  "unix:abstract=/tmp/dbus-9FhaHQgKgC,guid=5bbc0287bbabea8056017084000005f2"
      1 Registered DEC:  true
      1 "sni-qt/3888" WARN  12:10:54.679 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
      1 Invalid parent:  0xc39e6a8 QApplication(0xbf89afb4, name = "bitcoin-qt")
   1420 Requesting child objects for an interface that is a virtual child itself.
      1 not the same:  QObject(0x0)  QWidget(0xc6c30f8, name = "qt_scrollarea_viewport")  at path:  "/org/a11y/atspi/accessible/208417016/1"
      1 Requesting child objects for an interface that is a virtual child itself.
     20 Creating accessible with different object than the original interface!
      1 show QLabel(0xcde6468, name = "label")
      1 Creating accessible with different object than the original interface!
      1 show QLabel(0xc5e2108, name = "label_2")
      1 Creating accessible with different object than the original interface!
      1 show QValidatedLineEdit(0xcdd71b0)
      1 Creating accessible with different object than the original interface!
  • I had bitcoin-qt crash with a "Segmentation fault" error when I tried to open the 'options' dialog.  Sometimes I'm able to see the options dialog, and sometimes it crashes when I try to open it.  I tried re-running bitcoin-qt, then immediately did settings->options, cancel, settings->options and it crashed then, after working the first time.  I've rebuilt with debugging symbols and got a stack trace:
Code:
Program received signal SIGSEGV, Segmentation fault.
0xb415012d in QSpiAdaptor::checkInterface() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
(gdb) where
#0  0xb415012d in QSpiAdaptor::checkInterface() const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#1  0xb41562e0 in QSpiAdaptor::GetChildren() const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#2  0xb4156c9e in QSpiAdaptor::getCacheItem() const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#3  0xb414aecc in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#4  0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#5  0xb414bb7d in QSpiAccessibleBridge::notifyAccessibilityUpdate(int, QAccessibleInterface*, int) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#6  0xb77ff39e in QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#7  0xb7829d5e in QListView::selectionChanged(QItemSelection const&, QItemSelection const&) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#8  0xb780943a in QAbstractItemView::qt_metacall(QMetaObject::Call, int, void**) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#9  0xb798d9e2 in QListView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#10 0xb78763e2 in QListWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#11 0xb6fe2b7d in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#12 0xb6ff1a6a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#13 0xb785fa9d in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#14 0xb7865c35 in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#15 0xb7866ca4 in QItemSelectionModel::select(QItemSelection const&, QFlags<QItemSelectionModel::SelectionFlag>) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#16 0xb78619e6 in QItemSelectionModel::select(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#17 0xb785fdc8 in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#18 0xb7872874 in QListWidget::setCurrentRow(int) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#19 0x08078b75 in OptionsDialog::OptionsDialog (this=0xbfffe510, parent=0x0) at src/qt/optionsdialog.cpp:85
#20 0x08068bea in BitcoinGUI::optionsClicked (this=0xbffff458) at src/qt/bitcoingui.cpp:308
#21 0x0827f170 in BitcoinGUI::qt_metacall (this=0xbffff458, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfffe648)
    at build/moc_bitcoingui.cpp:110
#22 0xb6fe2b7d in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#23 0xb6ff1a6a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#24 0xb726883d in QAction::triggered(bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#25 0xb7268adb in QAction::activate(QAction::ActionEvent) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#26 0xb7711b13 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#27 0xb77183af in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#28 0xb771b0f5 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#29 0xb72c9f98 in QWidget::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#30 0xb7719b6c in QMenu::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#31 0xb726fd54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#32 0xb7275dbb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#33 0xb6fdc19e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#34 0xb7270d15 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#35 0xb72fd9fa in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#36 0xb72fbe4d in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#37 0xb732824c in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#38 0xb6a8b25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#39 0xb6a8b990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#40 0xb6a8bc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#41 0xb700aada in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#42 0xb7327e3a in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#43 0xb6fdb1dd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#44 0xb6fdb421 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#45 0xb6fe019d in QCoreApplication::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#46 0xb726d8f4 in QApplication::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#47 0x08064eb9 in main (argc=1, argv=0xbffff664) at src/qt/bitcoin.cpp:154
(gdb)
I then tried renaming my ~/.bitcoin/ folder and restarting.  After that I had a much harder time getting it to crash.  The options dialog appeared fine 5 or 6 times.  I encrypted my (new, empty) wallet, and everything was still fine.  Then I tried to change the passphrase a got a different crash:
Code:
Creating accessible with different object than the original interface!
Creating accessible with different object than the original interface!
not the same:  QObject(0x0)  QPushButton(0x8c4efb0)  at path:  "/org/a11y/atspi/accessible/147124144"
not the same:  QObject(0x0)  AskPassphraseDialog(0xbfffe520, name = "AskPassphraseDialog")  at path:  "/org/a11y/atspi/accessible/3221218592"

Program received signal SIGSEGV, Segmentation fault.
0xb7762fe4 in QAbstractScrollArea::viewport() const () from /usr/lib/i386-linux-gnu/libQtGui.so.4
(gdb) where
#0  0xb7762fe4 in QAbstractScrollArea::viewport() const () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#1  0xb404c7b2 in ?? () from /usr/lib/i386-linux-gnu/qt4/plugins/accessible/libqtaccessiblewidgets.so
#2  0xb414a0ab in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#3  0xb41505bb in QSpiAdaptor::getChild(int) const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#4  0xb4156426 in QSpiAdaptor::GetChildren() const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#5  0xb4156c9e in QSpiAdaptor::getCacheItem() const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#6  0xb414aecc in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#7  0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#8  0xb414b027 in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#9  0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#10 0xb414b554 in QSpiAccessibleBridge::objectToAccessible(QObject*) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#11 0xb4167fa4 in QSpiAccessible::getParentReference() const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#12 0xb4156ba8 in QSpiAdaptor::getCacheItem() const ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#13 0xb414aecc in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#14 0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#15 0xb414bb7d in QSpiAccessibleBridge::notifyAccessibilityUpdate(int, QAccessibleInterface*, int) ()
   from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#16 0xb77ff39e in QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#17 0xb7683b07 in QAbstractButton::setText(QString const&) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#18 0xb772663b in QPushButton::QPushButton(QString const&, QWidget*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#19 0xb76b647f in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#20 0xb76b67c6 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#21 0xb76b7041 in QDialogButtonBox::setStandardButtons(QFlags<QDialogButtonBox::StandardButton>) ()
   from /usr/lib/i386-linux-gnu/libQtGui.so.4
#22 0x0827cfd5 in Ui_AskPassphraseDialog::setupUi (this=0x8c24ff0, AskPassphraseDialog=0xbfffe520)
    at build/ui_askpassphrasedialog.h:108
#23 0x0827b352 in AskPassphraseDialog::AskPassphraseDialog (this=0xbfffe520, mode=AskPassphraseDialog::ChangePass,
    parent=0xbffff458) at src/qt/askpassphrasedialog.cpp:16
#24 0x0806aa59 in BitcoinGUI::changePassphrase (this=0xbffff458) at src/qt/bitcoingui.cpp:594
#25 0x0827f1ff in BitcoinGUI::qt_metacall (this=0xbffff458, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbfffe648)
    at build/moc_bitcoingui.cpp:115
#26 0xb6fe2b7d in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#27 0xb6ff1a6a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#28 0xb726883d in QAction::triggered(bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#29 0xb7268adb in QAction::activate(QAction::ActionEvent) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#30 0xb7711b13 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#31 0xb77183af in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#32 0xb771b0f5 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#33 0xb72c9f98 in QWidget::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#34 0xb7719b6c in QMenu::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#35 0xb726fd54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#36 0xb7275dbb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#37 0xb6fdc19e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#38 0xb7270d15 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#39 0xb72fd9fa in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#40 0xb72fbe4d in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#41 0xb732824c in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#42 0xb6a8b25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#43 0xb6a8b990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#44 0xb6a8bc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#45 0xb700aada in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#46 0xb7327e3a in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#47 0xb6fdb1dd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/i386-linux-gnu/libQtCore.so.4
#48 0xb6fdb421 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#49 0xb6fe019d in QCoreApplication::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#50 0xb726d8f4 in QApplication::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#51 0x08064eb9 in main (argc=1, argv=0xbffff664) at src/qt/bitcoin.cpp:154

dooglus
Legendary
*
Offline Offline

Activity: 2002



View Profile
October 24, 2011, 08:13:24 PM
 #17

I had bitcoin-qt crash with a "Segmentation fault" error when I tried to open the 'options' dialog.

Running this command seems to have stopped the crashes:
Code:
sudo apt-get remove qt-at-spi

Package qt-at-spi is installed by default when you install Ubuntu 11.10.  It looks like this is a known bug in ubuntu's qt-at-spi package.

You might want to include a note in the instructions about this.  I had tried testing the Qt bitcoin client when it was first merged to the master branch but gave up due to these crashes.  If I had known then that uninstalling qt-at-spi would fix them, I wouldn't have given up on the Qt client.

Gavin Andresen
Legendary
*
qt
Offline Offline

Activity: 1652


Chief Scientist


View Profile WWW
October 24, 2011, 10:51:55 PM
 #18

You might want to include a note in the instructions about this.

You == me?

There's a sticky here about creating a pull request, it'd be most excellent if you could make you==you and fix the doc/readme-qt.rst file.

I'll try hard to remember to mention this for the 0.5 release notes, but I'll warn you I'm really good at forgetting things.

How often do you get the chance to work on a potentially world-changing project?
dooglus
Legendary
*
Offline Offline

Activity: 2002



View Profile
October 24, 2011, 11:24:36 PM
 #19

There's a sticky here about creating a pull request, it'd be most excellent if you could make you==you and fix the doc/readme-qt.rst file.

See https://github.com/bitcoin/bitcoin/pull/592

dooglus
Legendary
*
Offline Offline

Activity: 2002



View Profile
October 29, 2011, 07:12:26 AM
 #20

The 'amount' column in the 'transactions' view isn't resizable, and doesn't fit in a value I recently sent.

xxx.xxxxxxxx BTC is ok, but -xxx.xxxxxxxx BTC doesn't fit, and I see xxx.xxxxx... instead (dots replacing the last 3 digits of the amount)

Three figure sums probably aren't all that uncommon to be sending, and it looks pretty ugly when the value doesn't fit in the box.

Pages: [1] 2 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!