qt-everywhere-src-5.12.3 qtwebengine-5.12.3

[Douglas R. Reno]

New point versions

I suspect these are security related due to recent Chromium vulnerabilities

[ken@…]

Yeah, at least for webengine.

​https://code.qt.io/cgit/qt/qtwebengine.git/tree/dist/changes-5.12.3/?h=v5.12.3 Chromium

---

• Security fixes from Chromium up to version 73.0.3683.75, including:

• CVE-2019-5787
• CVE-2019-5789
• CVE-2019-5790
• CVE-2019-5791
• CVE-2019-5792
• CVE-2019-5793
• CVE-2019-5794
• CVE-2019-5795
• CVE-2019-5797
• CVE-2019-5802
• CVE-2019-5803
• Security issue 905509
• Security issue 906437
• Security issue 906652
• Security issue 906739
• Security issue 913212
• Security issue 914511
• Security issue 916874
• Security issue 917608
• Security issue 917707
• Security issue 919340
• Security issue 919572
• Security issue 924905
• Security issue 929088
• Security issue 931640
• Security issue 938251
• Security issue 933743

(whatever those turn out to be), as well as the usual bugfixes throughout Qt.

[ken@…]

Good news and bad news: On an 8.4 machine, upgrading only qtwebengine (from 5.12.2) works, and falkon works. On my newest svn build (gcc-8.3.0), Qt itself built fine, but I have not yet managed to build qtwebengine - first attempt got a segmentation fault (will need to power down this box and check the DRAM), second attempt failed without any obvious explanation:

[8893/14807] /usr/bin/g++ -MMD -MF obj/v8/v8_base/v8_base_jumbo_40.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 -DENABLE_MINOR_MC -DV8_INTL_SUPPORT -DV8_USE_SNAPSHOT -DV8_CONCURRENT_MARKING -DV8_EMBEDDED_BUILTINS -DV8_TARGET_ARCH_X64 -DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC -I. -Igen -I../../../../src/3rdparty/chromium -I../../../../src/3rdparty/chromium/v8 -Igen/v8 -Igen -Igen -I../../../../src/3rdparty/chromium/v8/include -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-dangling-else -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-unused-parameter -fno-omit-frame-pointer -fvisibility=hidden -Wno-strict-overflow -Wno-return-type -O3 -fno-ident -fdata-sections -ffunction-sections -g0 -std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -c gen/v8/v8_base_jumbo_40.cc -o obj/v8/v8_base/v8_base_jumbo_40.o
FAILED: obj/v8/v8_base/v8_base_jumbo_40.o 

[ken@…]

Replying to ken@…:

(will need to power down this box and check the DRAM)

Indeed, the DRAM has become faulty.

[ken@…]

Although this came only a month after the .2 release, and does contain a lot of CVE fixes in (at least) webengine, it might have been planned for now. I've found a draft schedule at ​https://wiki.qt.io/Qt_5.12_Release - all being well, .4 will be at the end of May and .5 at the end of August.

Of course, the book will probably move to 5.13 when that comes out.

I assume that my second webengine failure on the recent system was due to the faulty DRAM. This builds and works fine on LFS-8.4 and earlier.

[ken@…]

r21478.

[Bruce Dubbs]

Milestone renamed