SUMMARY Ruqola failed to start today because it couldn't find libPlasmaActivities.so.6 The plasma-activities package exists and has installed libPlasmaActivities.so.6.5.0 but it has created the wrong symlink. root@hephaistos /usr/lib/x86_64-linux-gnu # dpkg -S libPlasmaActivities.so.7 plasma-activities: /usr/lib/x86_64-linux-gnu/libPlasmaActivities.so.7 Link name should end in "6" STEPS TO REPRODUCE 1. ls /usr/lib/x86_64-linux-gnu/libPlasmaActivities.so* OBSERVED RESULT /usr/lib/x86_64-linux-gnu/libPlasmaActivities.so.6.5.0 /usr/lib/x86_64-linux-gnu/libPlasmaActivities.so.7 EXPECTED RESULT /usr/lib/x86_64-linux-gnu/libPlasmaActivities.so.6 /usr/lib/x86_64-linux-gnu/libPlasmaActivities.so.6.5.0 SOFTWARE/OS VERSIONS Operating System: KDE neon User Edition KDE Plasma Version: 6.5.0 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.14.0-33-generic (64-bit) Graphics Platform: X11
abi was broken in plasma-activities thus the solib bump - https://invent.kde.org/plasma/plasma-activities/-/commit/690d377810f775b0e4e7512f9516c8a9ba123d4f all downstreams (including ruqola) where rebuilt against the new solib and snapshot to user edition
The solib version wasn't bumped. If that had been the case libPlasmaActivities.so.7 would be a link to libPlasmaActivities.so.7.x.y So the symlink has the correct version but the libraries themselves have been built with the wrong one, no?
apologies i only addressed the ruqola not starting part of the bug. unfortunately this appears tobe an upstream issue. the link in my previous comment shows that the solib was indeed bumped from 6 to 7 and neon build logs and kde invent build logs both show that the current situation is that libPlasmaActivities.so.6.6.0 points to libPlasmaActivities.so.7 .. https://invent.kde.org/plasma/plasma-activities/-/jobs/4023505#L476 https://build.neon.kde.org/job/noble_release_neon-packaging_plasma-activities_bin_amd64/32/artifact/result/plasma-activities_6.6.0-0zneon+24.04+noble+release+build33_amd64.deb.info.txt
(In reply to Kevin Krammer from comment #2) > If that had been the case libPlasmaActivities.so.7 would be a link to > libPlasmaActivities.so.7.x.y No. The soversion is one thing, the library version is a different thing. The soversion *usually* matches the major part of the library version, but it doesn't *have to*. There are many other KDE libraries where they don't match: libKExiv2, libgwenview, libKF6Konq, libdolphinvcs. The only thing that matters for the linker is the soversion, it doesn't care about the version of the library the symlink points to.