<!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->
When I build v0.17.0 myself on OS X (Sierra, 10.12.6) with QT 5.11.2 installed from Homebrew -- but NOT when I use the build downloaded from bitcoincore.org -- I experience glitches in which certain widgets do not refresh when they should.
In particular, when I click "Use available balance" in the Send tab, nothing happens -- the balance field does not update at all until I do one of the following: click in the balance field, open the debug window, change tabs and change back, switch to another app. At that time it updates to show my whole available balance.
This ONLY happens when I build bitcoin-qt myself, not with the binaries downloaded from bitcoincore.org.
I say "widgets" plural because I found that the same thing happens to a QPushButton I have created in a new QDialog -- when I call setEnabled(false) on it, it does not turn grey until I either change focus as above (e.g. switch to another app), or call ui->theButton->repaint(). @Sjors suggested on IRC that my Qt version might be to blame, but I will note that my OS X version is also quite outdated at this point.
<!-- Describe the issue -->
<!--- What behavior did you expect? -->
<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->
<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
<!-- Any extra information that might be useful in the debugging process. -->
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
