< YaNySS> Hello
< BlueMatt> gmaxwell: ugh, I'll see if I can find someone at canonical and tell them they're off letting people get scammed
< BlueMatt> but probably not
< BlueMatt> cause canonical dgaf
< gmaxwell> can you unpack whats actually going on there?
< BlueMatt> yea, so ubuntu decided that apt was confusing and instead of using apt for shit they want to push people towards "snaps" (some new canonical standard that "everyone else is also going to adopt, but for real this time)
< BlueMatt> so it says bitcoin isnt installed via the snap installer thinggy (the ubuntu software center)
< BlueMatt> but its installed via ppa (which, btw, completely doesnt work
< gmaxwell> and there is something in snap that is of dubious origin?
< BlueMatt> in this case I cant tell cause the website doesnt appear to give me a good way to see the package source
< BlueMatt> but if nothing else its clearly out of date
< BlueMatt> still shipping 15.1 as "latest stable" and 16.0 as "latest alpha" or some shit
< BlueMatt> so should be pulled
< gmaxwell> that PR... is it potentially the same issue that leaves 0.17 not working in the latest fedora?
< BlueMatt> and the "Developer website" goes to bitcoinclassic soooooo
< BlueMatt> gmaxwell: probably?
< BlueMatt> afaict openssl 1.1 is completely 100% fucked for bitcoin-qt
< BlueMatt> you cant even build with it on 32-bit machines
< gmaxwell> (I'm looking for the PR)
< BlueMatt> wait, what pr?
< BlueMatt> yea, but shouldnt that not be an issue in 0.17-release?
< gmaxwell> We should try to get people to include backtraces in PRs/Issues so we can match new crashes against prior backtraces.
< BlueMatt> err,
< BlueMatt> yea, sorry, the issue that I mentioned in 14754 is
< gmaxwell> BlueMatt: I don't think 14403 is in, I thought 0.1. was a the mac installer thing
< BlueMatt> oh, its not
< BlueMatt> ffs, so 0.17-release is completely inoperable? seems like we should do an 0.17.1, then?
< gmaxwell> -release is inoperable with super duper new QT. To the best o my understanding.
< BlueMatt> i mean its in a released shipping version of ubuntu
< BlueMatt> so it cant be /that/ new, but, fair
< BlueMatt> anyway, can I just remove bip70 now? :p
< gmaxwell> hold up, I'm not sure that those are the same issues.
< BlueMatt> I can test tomorrow
< gmaxwell> It just sounded vaguely related to me (new distro + bip70 + crash on start)
< gmaxwell> you gave a backtrace but the posted issue doesn't give one. but looking at yours looks likeit could be related to me.
< gmaxwell> s/crash/deadlock
< gmaxwell> "
< gmaxwell> With Qt 5.11.2, the configuration tweak is not only redundant but in
< gmaxwell> fact provokes a deadlock due to a bug in Qt 5.11.2. Since the deadlock
< gmaxwell> occurs at the early startup stage of bitcoin-qt, it renders bitcoin-qt
< gmaxwell> entirely non-functional "
< gmaxwell> sounds like your issue.
< BlueMatt> yea, indeed
< gmaxwell> in any case there are a couple other kinda dumb bugs in 0.17 that we should get fixes out for...
< gmaxwell> but obviously "doesn't run" is a big one! :P
< BlueMatt> yea, lol
< gmaxwell> BlueMatt: I think fixing your ubuntu issue should be a high priority... hopefully it's already fixed by the aformentioned PR.
< BlueMatt> I presume it is, but, yea, having the latest release not run on stock released ubuntu is....not good
< gmaxwell> it works if you use our binaries.
< gmaxwell> AFAIK
< BlueMatt> cause old static linked qt? would make sense
< gmaxwell> Yep. (also if it didn't the number of reports we'd be getting would be higher)
< BlueMatt> no idea where i was supposed to report that, but, seriously, fuck canonical
< gmaxwell> BlueMatt: thanks... perhaps we should up priority of updating the PPA! :P
< BlueMatt> hmm? the ppa has been pretty reliably up-to-date of late
< BlueMatt> you'll note the snaps in this case were pretty clearly some bitcoin classic troll
< gmaxwell> I thought the PPA can't to 0.17.0 because of the aformentioned bug?
< BlueMatt> which I presume is at least partially why they havent been updated since classic flamed
< BlueMatt> oh, the ppa has 0.17, it just doesnt work on the latest ubuntu
< gmaxwell> oh jesus. it's bitcoin "classic"?
< BlueMatt> no idea, the link to the "developer site" is bitcoin classic
< BlueMatt> i mean its clearly low-effort going on there
< gmaxwell> so it's either classic or the packager is especially ignorant.
< BlueMatt> definitely at least the second
< gmaxwell> (I've seen other people get tricked into thinking that 'classic' is the orignal bitcoin. .. the most amusing of which was some post after BU caught fire that tried to claim that BU's problems were mostly because the original bitcoin software was such crap, and then went after a bunch of bugs in 'classic' that either never were in Bitcoin or had long since been fixed. :P )
< BlueMatt> sounds about like it
< promag> Lauda: see #12721
< gribble> https://github.com/bitcoin/bitcoin/issues/12721 | Qt: remove "new" button during receive-mode in addressbook by jonasschnelli · Pull Request #12721 · bitcoin/bitcoin · GitHub
< Lauda> Oh, thanks!
< promag> also see #14573
< gribble> https://github.com/bitcoin/bitcoin/issues/14573 | qt: Add Window menu by promag · Pull Request #14573 · bitcoin/bitcoin · GitHub
< promag> The idea is to promote "Receive" tab and request payment
< bitcoin-git> [bitcoin] merland opened pull request #14755: Remove redundant readme info in /doc (master...issue-14639) https://github.com/bitcoin/bitcoin/pull/14755
< bitcoin-git> [bitcoin] promag opened pull request #14756: Improve by using argparse and getpass modules (master...2018-11-improve-rpcauth.py) https://github.com/bitcoin/bitcoin/pull/14756
< bitcoin-git> [bitcoin] practicalswift opened pull request #14757: Avoid reading uninitialized variables in serialization code (triggered when running "make check") (master...avoid-read-of-uninitialized-variable) https://github.com/bitcoin/bitcoin/pull/14757
< bitcoin-git> [bitcoin] practicalswift closed pull request #14757: Avoid reading uninitialized variables in serialization code (triggered when running "make check") (master...avoid-read-of-uninitialized-variable) https://github.com/bitcoin/bitcoin/pull/14757
< bitcoin-git> [bitcoin] promag opened pull request #14760: Log env path in BerkeleyEnvironment::Flush (master...2018-11-logmultienvflush) https://github.com/bitcoin/bitcoin/pull/14760
< MarcoFalke> Anyone has an idea how to disable compilation of this: crypto/sha256_sse4.cpp:44:9: error: unknown token in expression
< MarcoFalke> "shl $0x6,%2;"
< wumpus> MarcoFalke: --disable-asm?
< gmaxwell> MarcoFalke: there is a configure option to disable asm
< gmaxwell> lol wumpus' answer was faster an more informative.
< MarcoFalke> I thought it excluded those files, but let me try
< wumpus> although, ideally it *should* detect lack of support for assembly in the compiler in autoconf and do that automatically
< wumpus> there's even been talk of removing disable-asm but I think edge cases such as this make it useful to keep
< MarcoFalke> wumpus: gmaxwell: Thanks, that worked.
< gmaxwell> What strange compiler are you using where it cant compile crypto/sha256_sse4.cpp ?
< MarcoFalke> xenial on travis
< MarcoFalke> gcc5.something that is
< gmaxwell> I wonder if trais has done something weird, becuase that code should compile fine with gcc5.
< MarcoFalke> Its odd, I thought they used gce for the sudo-vms, but it would compile sse41.cpp on gce for me
< MarcoFalke> ok, travis is wrapped in docker and I used the gce without docker. Maybe it was that.
< bitcoin-git> [bitcoin] mmachicao opened pull request #14761: Tests : timedata : median file filter shall not grow beyond size (master...timedata_tests) https://github.com/bitcoin/bitcoin/pull/14761
< ap4lmtree> hi
< ap4lmtree> in bitcoingui.cpp it has a bunch of #include Qaction QApplication ... that is the main info for the graphics right?
< ap4lmtree> where did QAction come from , is it generic that many people use in programs?
< achow101> ap4lmtree: it's from the Qt library
< ap4lmtree> ok
< ap4lmtree> i took a class on c++ and java, but we didn't get to gui and using frameworks
< ap4lmtree> so i will have to learn this stuff
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/6d58a5c3b055...09f1d7fe7243
< bitcoin-git> bitcoin/master c54e5a4 Murray Nesbitt: Remove unreferenced boost headers
< bitcoin-git> bitcoin/master 09f1d7f MarcoFalke: Merge #14718: Remove unreferenced boost headers...
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #14718: Remove unreferenced boost headers (master...clang_warnings) https://github.com/bitcoin/bitcoin/pull/14718
< meshcollider> wumpus: are you around?
< provoostenator> #14718 breaks master test/lint/lint-includes.sh because fstream.hpp is no longer used.
< gribble> https://github.com/bitcoin/bitcoin/issues/14718 | Remove unreferenced boost headers by murrayn · Pull Request #14718 · bitcoin/bitcoin · GitHub
< provoostenator> (I'll make a PR)
< bitcoin-git> [bitcoin] Sjors opened pull request #14763: Remove filesystem/fstream from EXPECTED_BOOST_INCLUDES (master...2018/11/expected_boost_includes) https://github.com/bitcoin/bitcoin/pull/14763
< provoostenator> I think Travis missed some issues (due to cache?) in the original PR... see comment on ^ (cc MarcoFalke)
< MarcoFalke> It wasn't run :(
< MarcoFalke> Looks like they still have problems with blacklisting.
< MarcoFalke> provoostenator: Best to add back that header
< gmaxwell> BlueMatt: did you confirm if that PR was also your ubuntu deadlock?
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #14764: travis: Run thread sanitizer (master...Mf1811-travisSanThread) https://github.com/bitcoin/bitcoin/pull/14764
< BlueMatt> gmaxwell: oh, oops, yes, I did, I forgot to update the issue, though