On Thu, Oct 28, 2021 at 12:44 PM Burt Holzman <b...@fnal.gov> wrote: > > On 10/28/2021 8:41 AM, Troy Dawson wrote: > > On Thu, Oct 28, 2021 at 4:56 AM Götz Waschk <goetz.was...@desy.de > > <mailto:goetz.was...@desy.de>> wrote: > > > > Am 26.10.21 um 04:27 schrieb Patrick J. LoPresti: > > I just like to add that this has already happened to me with an Ubuntu > > 20.04 LTS container running on > > SL7: > > > > [wgs34:U20] ~ % gnuplot-qt > > gnuplot-qt: error while loading shared libraries: libQt5Core.so.5: > > cannot open shared object file: No such file or directory > > [wgs34:U20] ~ % ldd /usr/bin/gnuplot-qt|fgrep Qt5 > > libQt5Network.so.5 => > > /lib/x86_64-linux-gnu/libQt5Network.so.5 > > (0x00007f6cf5da9000) > > libQt5Gui.so.5 => /lib/x86_64-linux-gnu/libQt5Gui.so.5 > > (0x00007f6cf57be000) > > libQt5Core.so.5 => not found > > > > > That doesn't have much to do with the container running on SL7, and more > > that your gnuplot-qt was compiled on a different qt5 than is in the > > container. > > > > Without more details I couldn't exactly say more than make sure your > > gnuplot-qt and qt5 libraries in yoru container are up to date. > > Actually, in this particular case, Qt added dependencies on kernel > syscalls (IIRC renameat2 maybe also getrandom) that show up upstream > from the current SL7 kernel. > > - B
That is good to know. I would have never guessed that. Thank you for letting me / us know. And Götz, thank you for doing the check on the other kernel. I would have replied to that one also, but I figured then I'm just spamming everyone. I help maintain the KDE Plasma desktop in EPEL 8 / 9, and I'm betting this is going to come up as a bug somewhere. It's good to know the real problem before someone brings me a bug. Thanks Troy
