https://bugs.kde.org/show_bug.cgi?id=417791
--- Comment #7 from scx.m...@gmail.com ---
I have an another theory!
Is it possible that the kde-frameworks-5-core18:kde-frameworks-5-core18-slot
slot is not mounted because it is not compatible with the system?
Let's look at the Qt5 libs that it provides:
$ find /var/lib/snapd/snap/kde-frameworks-5-core18 -xtype f -iname
'libQt5Core.so.5*' 2>/dev/null | xargs -I{} file '{}'
/var/lib/snapd/snap/kde-frameworks-5-core18/30/usr/lib/x86_64-linux-gnu/libQt5Core.so.5:
symbolic link to `libQt5Core.so.5.12.3'
/var/lib/snapd/snap/kde-frameworks-5-core18/30/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12:
symbolic link to `libQt5Core.so.5.12.3'
/var/lib/snapd/snap/kde-frameworks-5-core18/30/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.3:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=252fcd9f736251377f96e559b953f9cb4b8fbdec, for
GNU/Linux 3.17.0, stripped
/var/lib/snapd/snap/kde-frameworks-5-core18/32/usr/lib/x86_64-linux-gnu/libQt5Core.so.5:
symbolic link to `libQt5Core.so.5.12.3'
/var/lib/snapd/snap/kde-frameworks-5-core18/32/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12:
symbolic link to `libQt5Core.so.5.12.3'
/var/lib/snapd/snap/kde-frameworks-5-core18/32/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.3:
ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=2742584b062a7248211733fb8a9365897d2db95a, for
GNU/Linux 3.17.0, stripped
As you can see, they are built for Linux 3.17.0. EL7, however, uses Linux
3.10.0-1062 by default (highly modified 3.10.0).
$ uname -r
3.10.0-1062.9.1.el7.x86_64
The best way to check this would be using kernel-lt or kernel-lt from ELRepo.
https://elrepo.org/tiki/kernel-lt
https://elrepo.org/tiki/kernel-ml
Actually, we've already hit a very similar problem with Flatpak in Jan 2019.
https://github.com/flathub/flathub/issues/805
https://bugs.kde.org/show_bug.cgi?id=403042
As you can see, Debian 8 and Ubuntu 14.04 LTS should be affected as well.
Anyway, neither core18, nor cantor itself should be a problem here.
$ file /var/lib/snapd/snap/core18/current/lib/x86_64-linux-gnu/libc-2.27.so
/var/lib/snapd/snap/core18/current/lib/x86_64-linux-gnu/libc-2.27.so: ELF
64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked
(uses shared libs), BuildID[sha1]=b417c0ba7cc5cf06d1d1bed6652cedb9253c60d0, for
GNU/Linux 3.2.0, stripped
$ file /var/lib/snapd/snap/cantor/current/usr/bin/cantor
/var/lib/snapd/snap/cantor/current/usr/bin/cantor: ELF 64-bit LSB shared
object, x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs),
for GNU/Linux 3.2.0, BuildID[sha1]=7c98f936a4d8ccd35cda1c62e128c9d66e8c16d9,
not stripped
As you can see, they are built for Linux 3.2.0.
Qt5, however, may use getentropy, so it requires Linux 3.17.0.
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/global/minimum-linux_p.h?id=4d9ac14bf8d1c1a33a2720c7f7dcaf8d912a592f#n77
However, it should be possible to build Qt5 without this feature.
https://phabricator.kde.org/R257:a029f2957e947f6e32fe8a595edb0ac553654e90
Although I'm not completely sure, I think that rebuilding
kde-frameworks-5-core18:kde-frameworks-5-core18-slot without getentropy should
enough to fix it.
Can you handle this?
--
You are receiving this mail because:
You are watching all bug changes.
