PI 1.8.8-8 and 1.8.8-9 : QtWebEngineProcess crashing

MartinN

Member
Jun 2, 2014
12
0
I am running PI on Linux, flavour opensuse Tumbleweed. After some package updates a few days ago, PI 1.8.8-8 crashed.
My hopes, that version 1.8.8-9 would not crash, did not hold.
What happens: the PI window itself reports no error, but the system journal constantly reports about coredump of several PI threads, running QtWebEngineProcess, like:
/opt/PixInsight/bin/libexec/QtWebEngineProcess --type=zygote
or with --type utility or --type renderer. A complete module trace list is:

Sep 25 13:37:11 t420.earth.sol systemd-coredump[4866]: [] Process 4862 (QtWebEngineProc) of user 1000 dumped core.

Found module linux-vdso.so.1 with build-id: c2766a83ee37eab9aaed82319445e3f4a9120444
Found module libgpg-error.so.0 with build-id: 4db4852a0ac95da57005de7e92fb7f99eccca826
Found module libbrotlicommon.so.1 with build-id: 6686aa325d4afdb805e780ca00c6c1ee8355c0ec
Found module libgcrypt.so.20 with build-id: b42217713b6dde01b56599aa5f277a19ebbcdc70
Found module libcap.so.2 with build-id: a102dd0c3ff0723fc709885886252606bf229f69
Found module liblz4.so.1 with build-id: c50fdf2323710302f507af09e1d71ecfd5e4f3ec
Found module libzstd.so.1 with build-id: 171a1a1f4fb732f38b5a392e24b33e0a53b2be94
Found module liblzma.so.5 with build-id: 114f5de77af42eeae25b95718dfee184e2cab587
Found module libbrotlidec.so.1 with build-id: b1a64db9f269d9241cf4642ab820373edf56af85
Found module libz.so.1 with build-id: ca0254f7e149a787d1aa310d7652cb9da10ddb6c
Found module libpng16.so.16 with build-id: 78afe6992bb3326434c28f8ba19ad875b6194850
Found module libbz2.so.1 with build-id: fb7461db07ad3fbbcdb675cc400776e9f930c70b
Found module libGLdispatch.so.0 with build-id: 0b3c70da800c6ed335da726e2b45861b7bef0fdd
Found module libGLX.so.0 with build-id: 0c25fbbbc67ec7a0ddde220758fb38d30ec3c2c7
Found module libsystemd.so.0 with build-id: 461dc9050d42026e14ad5e402393f22cd8fbd809
Found module libXau.so.6 with build-id: 6380e242b53ea6076bea41d5367d97dfd612fca1
Found module libuuid.so.1 with build-id: 9b7d6480706906dded03b515b5043a297f623166
Found module libfreetype.so.6 with build-id: 6105a21864cc3e3b787dd5083b0cb42b48b6294e
Found module libXrender.so.1 with build-id: adc3163c6cede1acb49fba991255c72bc35b5fa2
Found module libplds4.so with build-id: 52e8bf6911daecbb43180f0ce23af4dbdf829163
Found module libplc4.so with build-id: 8170e46f00d29c1b89a25aaa1705161b173b5828
Found module libGL.so.1 with build-id: 26ee9171ccc1d35b9e0e9b5f08192bf87d94dc22
Found module libQt5QmlModels.so.5 with build-id: ea3490caf75d16cb980135adc8e1bb2e40743b20
Found module libpcre.so.1 with build-id: b24ed45c51c6b54dfc2f5a9b3c7358d08b95e8ff
Found module libasound.so.2 with build-id: 5b782d3522c78e5d3519b5c8bb8dc4be96611bc6
Found module libdbus-1.so.3 with build-id: 99304aa3214776a38dfac678bb099e585d118e8b
Found module libxcb.so.1 with build-id: 4159a44f03f9d58e122f48f915e7f6043bd222bc
Found module libX11-xcb.so.1 with build-id: b4e14f3158e791b1b5289721da7730f0d56862bf
Found module libfontconfig.so.1 with build-id: f0ddafe4ecbd4a3dcd47a17199b355db9d402b04
Found module libexpat.so.1 with build-id: e4a8afcbd0f5d33569c34d0831dbd1ee2aaa306b
Found module libXtst.so.6 with build-id: b7e4bb0523b8321e02f33087bf15ae39adaf7e75
Found module libXrandr.so.2 with build-id: 271a76ced980079dcb166b428bea70a7ec6aee78
Found module libXfixes.so.3 with build-id: f90113ce932615cf1a1025df30ae41298780decf
Found module libXext.so.6 with build-id: 7e79a4e63803a2196ae437875924877e38c8e959
Found module libXdamage.so.1 with build-id: a75f0f176f899ba7c1b02c833f974ee6d17aa7b7
Found module libXcomposite.so.1 with build-id: 4c984f15e3d7dbe19cc6340a0d832feeb9688905
Found module libX11.so.6 with build-id: 70a7c45b5f0c4472731a74c0882c7e30581c0db8
Found module libnspr4.so with build-id: ed9e004d6624fd0c9794fc2e2b509add45b9990b
Found module libnssutil3.so with build-id: f791c9b65a298bd0f88d35955fa7ebc98711c4f5
Found module libnss3.so with build-id: 17316e67827d1cfd193a039d7ca12a29c44922f7
Found module librt.so.1 with build-id: 39cbea9d290d36714fd14b024448cbddb7c58196
Found module libQt5Network.so.5 with build-id: 22172e60dd5b33eb52d82939b20dead1f5c6339d
Found module libQt5Gui.so.5 with build-id: 87f5dad6216f5f9437fcabf63628c9dad0aa5049
Found module libQt5Qml.so.5 with build-id: 78f7d9f064dc399554e27270a902bedd5c76eb5b
Found module libQt5WebChannel.so.5 with build-id: 363173ea2e31125923ce89ad5e0812c7558b9596
Found module libQt5Quick.so.5 with build-id: d9c95bd32c378569ffeadda97faacf2ff5fb10a0
Found module libQt5Positioning.so.5 with build-id: 9f2434071867fd7ade7572ba3b9b79c328b63aaf
Found module ld-linux-x86-64.so.2 with build-id: deb31dcbf1b8f27be272e9a3872f66e8de7e4a3a
Found module libgcc_s.so.1 with build-id: 47fa0449296fc2bf230270386fc95a0affa5861e
Found module libm.so.6 with build-id: b69b9e3cd51d7e4f6c91bd4f6566dddfe1f535d2
Found module libglib-2.0.so.0 with build-id: 153b59720284c57e9da8b5831731aa3b31372dc7
Found module libdl.so.2 with build-id: c9d000a19f8f757623bb1378026ac06b3bd23841
Found module libpthread.so.0 with build-id: fc089d94c8efebad67152ae25603e1ed0afabfc5
Found module libc.so.6 with build-id: 275df9362092035f90b2a4d4bdde998a6524a74c
Found module libstdc++.so.6 with build-id: b9e395f94796e963124fbed84554da09711827af
Found module libQt5WebEngineCore.so.5 with build-id: ef6d8d88681654aa04856052417900cfe976fb12
Found module libQt5Core.so.5 with build-id: d2154cb2f6ff49cbf0be1c0805d6d15939f84ed7
Found module QtWebEngineProcess with build-id: d7ef50371376b6afb33bfa85a18c4951767f83e6
Stack trace of thread 1:
#0 0x00007f9a060272ad __clone3 (libc.so.6 + 0x1122ad)

Do I have to wait for a fix of a failing library or do we have a problem in PI ?

Kind regards
Martin
 

Juan Conejero

PixInsight Staff
Sep 2, 2004
8,156
344
57
Valencia, Spain
pixinsight.com
Hi Martin,

This cannot be reproduced.

After some package updates a few days ago, PI 1.8.8-8 crashed.
From this I understand that before the package updates PixInsight was running well, and the problems started after the package updates. In such case this cannot be a problem caused by PixInsight.

The QtWebEngineProcess executable included in the PixInsight distribution is not intended to be executed as a standalone process. It can only be executed by the PixInsight core application.

Current versions of PixInsight are stable on all supported platforms, and very especially on Linux. Please provide a repeatable pattern or a list of steps to reproduce the problem, otherwise this is a machine-specific issue.
 

MartinN

Member
Jun 2, 2014
12
0
Hi Juan,

that's true, before the package updates, PixInsight was running well. I installed more than 3000 package updates on Sep 22 on my system (using zypper dup).
*
My intention on noting "QtWebEngineProcess" was risen from output of systemd-coredump in the journal.
The "/opt/PixInsight/bin/libexec/QtWebEngineProcess --type=zygote" is just part of output from command "ps -ef|grep Qt", likely a thread of PixInsight itself... or not ?
Is PixInsight not depending on any installed QT libraries, but running all needed QT code from its own directories below /opt/PixInsight ?
*
I am amazed on stability of PixInsight on Linux, running it preferably only there ;-)
But if this problem is a machine specific issue, I have two different machines here (Desktop w/ 32GB-i7-2600 and Thinpad T420 w/ 16GB-i5-2540M) suffering from it :-(
Maybe the cause can be nailed down to some package updates around QT5; there were a lot indicating versions like 5.15.2+ (e.g. libqt5-qtgraphicaleffects-5.15.2+kde2-1.2.x86_64), 5.15.6 or even 5.22.5, which are different from 5.15.5 LTS.
Especially, package libqt5-qtwebengine-5.15.6-1.2.x86_64 has been installed. Is this the culprit ?
Should I revert to libqt5-qtwebengine-5.15.5-1.2.x86_64 (if possible at all) ?
*
Or do I have to bet for further package updates on opensuse tumbleweed coming in the next days/weeks (what a pain :( ) until PixInsight is running again ?

Kind regards
Martin
 

Juan Conejero

PixInsight Staff
Sep 2, 2004
8,156
344
57
Valencia, Spain
pixinsight.com
Is PixInsight not depending on any installed QT libraries, but running all needed QT code from its own directories below /opt/PixInsight ?
Yes. The PixInsight distribution includes its own Qt libraries on all supported platforms. The Qt libraries installed by your Linux distribution are irrelevant.

Maybe the cause can be nailed down to some package updates around QT5; there were a lot indicating versions like 5.15.2+ (e.g. libqt5-qtgraphicaleffects-5.15.2+kde2-1.2.x86_64), 5.15.6 or even 5.22.5, which are different from 5.15.5 LTS.
Certainly a good mess! Qt 5.22 does not exist. The latest Qt 5 version is 5.15.6, which is a commercial LTS version (as is 5.15.5) that no Linux distribution can include under normal licensing conditions. With 5.22.5 I assume you are referring to KDE Plasma libraries.

The problems you are reporting don't happen under normal conditions and denote a probable system corruption. The way you are updating your system looks chaotic. I strongly recommend that you use a stable and fully verified Linux distribution if you want to have a system seriously configured for productivity. Our current reference platform is Kubuntu 20.04 LTS.
 

MartinN

Member
Jun 2, 2014
12
0
Right, version 5.22.5 was not Qt relevant; I took this version from the wrong line.
*
The way I am updating the system is not caotic. Opensuse tumbleweed has just a rolling release, running the most recent package versions available. These have been tested for stability and dependencies. Though there is a slight risk for problems due to bleeding edge package versions, I didn't suffer any problem when running PixInsight on it up to lately.
*
I analyzed the stack trace above, and found out (comparing the build-id) that
libc.so.6 with build-id: 275df9362092035f90b2a4d4bdde998a6524a74c
is from my system, but
libstdc++.so.6 with build-id: b9e395f94796e963124fbed84554da09711827af
is not loaded from tumbleweed, its delivered by PixInsight.
libstdc++ is suffixed by 6.0.29 on both PixInsight and tumbleweed. No surprise at all, the have a different file size.
But the list of Undefined symbols is different in them.
I assume the version of libstdc++ delivered with PixInsight requires at least one missing symbol in libc.so.6
libc.so.6 is version 2.34-1.2 now on tumbleweed, but was updated from version 2.33-9.1 with the big package updates mentioned above.
Since then PixInsight's QtWebEngineProcess has a problem on tumbleweed.
*
Eventually I could invest efforts to install current reference platform Kubuntu 20.04 LTS to run PixInsight.
*
On the other: hand it might just be a question of time, when PixInsight's QtWebEngineProcess would even dump core there (on Kubuntu 20.04 LTS), and the rebuilt version of PixInsight (1.8.8-10 or higher) would then even run again on tumbleweed... who knows ?
*
So, at this point I will not bother any longer. It seems I have to find a solution for myself...

Anyhow, keep on the good work !
Kind regards
Martin
 

MartinN

Member
Jun 2, 2014
12
0
Hi Juan,

not yet... though system's libstdc++ is used, the coredumps continue.
libQt5WebEngineCore is the next lib in chain. I dared to bring this out, too, but then starting PixInsight I got
/opt/PixInsight/bin/PixInsight: /opt/PixInsight/bin/lib/libQt5Gui.so.5: version `Qt_5.15.2_PRIVATE_API' not found (required by /lib64/
libQt5WebEngineCore.so.5)
/opt/PixInsight/bin/PixInsight: /opt/PixInsight/bin/lib/libcrypto.so.1.1: version `OPENSSL_1_1_1d' not found (required by /lib64/libss
h.so.4)

Kind regards
Martin
 

Juan Conejero

PixInsight Staff
Sep 2, 2004
8,156
344
57
Valencia, Spain
pixinsight.com
libQt5WebEngineCore is the next lib in chain. I dared to bring this out
Of course you cannot do that. All Qt libraries must be the ones included in the PixInsight/bin/lib directory or nothing will work.

Definitely, something very complicated is going on with your system and current PixInsight versions. I am completely out of ideas. This does not happen with all of the Linux distributions that we have tested. Admittedly, openSUSE is not one of them.
 

MartinN

Member
Jun 2, 2014
12
0
The libQt5WebEngineCore test was just a quick shot, to see what happens ;-)
Yes, due to the PixInsight distribution including its own Qt libraries on all supported platforms, this test was very likely to fail.

Digging around I found another dependency, even on 20.04 LTS: if newer linux kernel headers, like those of 5.13 from kernel-ppa/mainline, are to be installed, glibc >= 2.33 is required. Though this requirement does not apply to the kernel 5.13 itself, the headers are required in case of development environments simply needing linux kernel headers.
There may be no requirement for a 5.13 kernel currently, when running 20.04 LTS.

So, I see that it's not that very complicated, what going on with my system and current PixInsight versions.

But for me, it seems to be only a question of time, when even PixInsights development environment must be able to compile w/ 5.13 linux kernel headers... when this is solved, and PixInsight is built, it would run again on tumbleweed.

Hopefully not that late like April 2025 :unsure:
Until then I have to switch to another platform or linux distribution :(
 
Last edited:

karolbe

New member
Apr 12, 2020
4
2
Hi,
I also have OpenSuse TW and unfortunately I ran into the same issue :-( Which is even more unfortunate as I purchased the commercial license just yesterday...

Is there any workaround?

This is related to the glibc 2.34 update, it broke many Electron based applications (Slack, MS Teams etc) a few days ago.

Looks like next Fedora, Ubuntu will be also affected, in fact any system with glibc 2.34. So hopefully there is a fix or at least workaround soon.
 
Last edited:

MartinN

Member
Jun 2, 2014
12
0
No workaround, really: in addition to tumbleweed, I installed Leap 15.3 in another partition (11GB would be sufficient), w/ a minimum KDE environment, and boot loader only installed to its /boot Partition (thus identical to / partition). Warnings on probably being unbootable ignored, because tumbleweed, when booted next time and its bootloader beeing updated, is so nice to include Leap 15.3 as bootable.
That way, you could get rid of Leap 15.3 lateron; or even keep it as a alternative or rescue system.
When installing Leap, and is asks for user definitions, you can even "import" users from tumbleweed. However, PixInsight needs to be installed in tw, too, but runs w/o problems.
At least, you can use the same swap partition and temporary working directories (better: partitions on SSDs mounted there) like those of tw.
Working on the same PixInsight projects, with unchanged directories, is possible then...
 

karolbe

New member
Apr 12, 2020
4
2
FYI I managed to fix it under TumbleWeed. I removed QT libs from PixInsight folder, made changes in the PixInsight.sh so it points to /lib64:

Code:
LD_LIBRARY_PATH=/lib64:/lib64/qt5/libexec:$dirname/lib:$dirname
LC_ALL=en_US.utf8
QT_PLUGIN_PATH=/lib64/qt5/plugins
QT_QPA_PLATFORM_PLUGIN_PATH=/lib64/qt5/plugins/platforms #$dirname/lib/qt-plugins/platforms
QT_QPA_PLATFORMTHEME=
QT_QPA_GENERIC_PLUGINS=
QT_AUTO_SCREEN_SCALE_FACTOR=0
QT_SCALE_FACTOR=1
QT_LOGGING_RULES='*=true'
QTWEBENGINEPROCESS_PATH=/lib64/qt5/libexec/QtWebEngineProcess
Now is the tricky part,I am not sure what else helped, but I think it is because this package was updated:

❯ rpm -qi libqt5-qtwebengine-5.15.6-2.1.x86_64
Name : libqt5-qtwebengine
Version : 5.15.6
Release : 2.1
Architecture: x86_64
Install Date: Thu 07 Oct 2021 10:47:51 AM CEST
Group : Development/Libraries/X11
Size : 155701116
License : LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only
Signature : RSA/SHA256, Mon 27 Sep 2021 02:49:45 AM CEST, Key ID b88b2fd43dbdc284
Source RPM : libqt5-qtwebengine-5.15.6-2.1.src.rpm
Build Date : Mon 27 Sep 2021 12:21:46 AM CEST
Build Host : sheep82
Packager : https://bugs.opensuse.org
Vendor : openSUSE

This package's changelog mentions a few glibc 2.34 fixes which I think were crucial: https://opensuse.pkgs.org/tumblewee...-qtwebengine-devel-5.15.6-2.1.x86_64.rpm.html
 

MartinN

Member
Jun 2, 2014
12
0
To fix it under TumbleWeed acting like you described above is a cool way :cool:
I will try it this weekend, too...
And yes: changelogs glibc 2.34 fixes are the key to success here. Question is, however, how long the complete QT libs from Tumbleweed are "old enough and compatible" with PixInsight's development environment. :unsure: