I've got a few issues with KDE after updating packages this morning.
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:15:1: plugin cannot be loaded for module "org.kde.plasma.private.taskmanager": Cannot load library /usr/lib/qt/qml/org/kde/plasma/private/taskmanager/libtaskmanagerplugin.so: (libKF5Screen.so.7: cannot open shared object file: No such file or directory)
world/libkscreen 5.26.5-1 (plasma) [installed: 5.27.0-1]
usr/lib/libKF5Screen.so.7
ldd: /usr/lib/libKF5Screen.so.7: No such file or directory
It looks like a similar issue than the one described in https://forum.artixlinux.org/index.php/topic,5101.msg32672.html
(I've downgraded the kdecoration pack to fix that one)
It feels like some change has excluded libraries from a bunch of (kde?) packages.
I feel this is that kwin update thing too, (hopefully) the actual solution will flow through in an update later (hopefully) today. I get the same using kwin for a wm under lxqt, so I'm assuming updating in tty2 will do the job at some point!
I ran in this exact issue, and KDE is fully broken right now.
After the update, we now have
/usr/lib/libKF5Screen.so.5.27.0
/usr/lib/libKF5Screen.so.8 -> libKF5Screen.so.5.27.0
But no
/usr/lib/libKF5Screen.so.8
Simply creating such a symlink sadly doesn't fix the problem.
Is there some workaround for this? My desktop is completely unusable at the moment :-(
https://forum.artixlinux.org/index.php/topic,5102.msg32675.html#msg32675
Hey, thanks for the hint! Manually buiding kwin and plasma-workspace actually fixed it!
I didn't had to change anything in the kwin PKGBUILD though (maybe this is already fixed?). Also, I passed --skippgpcheck to makepkg. And I had to tell pacman to --overwrite \* when installing the plasma-workspace package (due to some doc file collisions with plasma-desktop).
But it works.
Hopefully, this will be fixed upstream really soon, as this is really severe breakage …
Should be OK now; pls try again
artist
Seems to work now. Thanks a lot for the quick fix :-)
Artix really needs a Bugzilla for such issues … this way, something like this could be canalized, and woult not be scattered in several forum posts …