Thanks! Also FYI, the glibc change was reverted for Impish:
https://launchpad.net/ubuntu/+source/glibc/2.34-0ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939993
Title:
glibc 2.34 causes q
FYI, I asked upstream to backport the Chromium patch:
https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/374204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939993
Title:
glibc 2.34 cau
This bug was fixed in the package qtwebengine-opensource-src -
5.15.5+dfsg-2
---
qtwebengine-opensource-src (5.15.5+dfsg-2) unstable; urgency=medium
* Add a patch to fix build with glibc ≥ 2.34 where SIGSTKSZ is no longer
a compile time constant.
* Backport Chromium patch to m
webengine in proposed should fix this
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1939993
Title:
glibc 2.34 causes qtwebengineprocess to crash or fail to
Hooray for slow builds. Let me know if you need me to do anything :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939993
Title:
glibc 2.34 causes qtwebengineprocess to crash or fail to start
To m
On 15/08/2021 21:49, Michael Hudson-Doyle wrote:
> That link certainly looks relevant. Which package does that need to
> apply to? qtwebengine-opensource-src? Can you do that or do you want me
> to try?
Yes, qtwebengine-opensource-src. I have been talking to the
debian/ubuntu qt maintainers, and
That link certainly looks relevant. Which package does that need to
apply to? qtwebengine-opensource-src? Can you do that or do you want me
to try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939993
Starting apps with QTWEBENGINE_CHROMIUM_FLAGS="--no-sandbox" seems to
make them work again, so as point out by the very nice people from
OpenSuse it seems to be this issue:
https://chromium-review.googlesource.com/c/chromium/src/+/2936184
--
You received this bug notification because you are a m
