LinuxQuestions.org - [SOLVED] Another strange thing with latest -current ( 30 March 2024 )

Hello all,
after upgrading to latest current I've found another strange thing that does not allow plasma to start.

startplasma-x11 in fact is linked to a previous version of libplist.

Code:

linux root ~# ldd /usr/bin/startplasma-x11 | grep libplist

        libplist-2.0.so.4 => /usr/lib64/libplist-2.0.so.4 (0x00007f25556cd000)

        libplist-2.0.so.3 => /usr/lib64/libplist-2.0.so.3 (0x00007f25551a8000)

but the slackpkg upgrade-all remove the 2.0.so.3, so I had to reinstall it form a previous -current to make kde working again:

Code:

linux root ~# ls -l /var/adm/packages/libplist*

-rw-r--r-- 1 root root 1630 Mar 30 12:54 /var/adm/packages/libplist-2.2.0-x86_64-3

-rw-r--r-- 1 root root 1636 Mar 30 12:36 /var/adm/packages/libplist-2.4.0-x86_64-2

linux root ~# slackpkg search libplist



Looking for libplist in package list. Please wait... DONE



The list below shows all packages with name matching "libplist".



[  upgrade  ] - libplist-2.2.0-x86_64-3 / libplist-2.4.0-x86_64-2

            --> libplist-2.4.0-x86_64-2



You can search specific files using "slackpkg file-search file".

This double linkage is there also for the startplasma-wayland:

Code:

linux root ~# ldd /usr/bin/startplasma-wayland | grep libplist 

        libplist-2.0.so.4 => /usr/lib64/libplist-2.0.so.4 (0x00007f2de2510000)

        libplist-2.0.so.3 => /usr/lib64/libplist-2.0.so.3 (0x00007f2de1fe9000)

Is this a mine problem or something that need to be adressed by the build ?

Thanks in advance

Pierluigi