KDE neon 5.19 User Edition (20.04/focal)
KDE Plasma: 5.19.4
KDE Frameworks: 5.72.0
Qt: 5.14.2
Kernel: 5.4.0-42-lowlatency

KSysGuard: 4:5.19.4-0xneon+20.04+focal+build7

For some reason, KSysGuard requires older libraries such as libvpx.so.5 and libx264.so.152, but from what I can tell those would've only been available in bionic.

Code: Select all

$ ls /usr/lib/x86_64-linux-gnu | grep -E 'lib(vpx|x264)'
libvpx.a
libvpx.so
libvpx.so.6
libvpx.so.6.2
libvpx.so.6.2.0
libx264.a
libx264.so
libx264.so.155


From APT, I also could only find libvpx6=1.8.2-1build1 and libx264-155=2:0.155.2917+git0a84d98-2.

On a side note, I guess it may actually require more older libraries than simply those two, cause tbh I only found out it also required libx264-152 after creating a symlink for libvpx5.

Re-enable any Mesa or driver related PPA you have, refresh and update (to install Focal versions of the PPA's packaging) , and try again.

claydoh wrote:Re-enable any Mesa or driver related PPA you have, refresh and update (to install Focal versions of the PPA's packaging) , and try again.

Thanks, confirmed working! (can't even being to guess how it just falls together, but I'm happy enough to know that it works!)

Ksysguard depends on some sensor related packages, which are connected to Mesa at some point, and the PPA's Bionic versioning of the Mesa related packages bung up the dependencies until they get updated to Focal. Or something like that.

I had all kinds of problems with ksysguard dependency issues too, but they were fixed when I used ppa-purge to remove the Kisak Mesa PPA before starting (I restored from a backup to get it to the initial state). I know it's best to revert PPAs when upgrading like that, but I have so many, and I'm lazy, so I gave it a shot without purging. The Mesa PPA was the only one that presented a problem, and the upgrade went well once it was removed.