July update broke the printer manager in KDE/systemsettings on all my computers here, missing “libpackagekitqt6.so.1” dependency.
I had to install “packagekit-qt6” (and packagekit as dependency) to make it work again.
If it can help someone…
1 Like
… Should never be used on an Arch-based system, because it throws your permissions wide open.
I agree that there’s obviously a packaging error — and ironically, over at Arch, because we inherit all of our Plasma-related packages from them unmodified — but really, do not use packagekit.
print-manager does not depend on packagekit so it sounds strange it would fix the print-manager
No, but the kcm does. And that’s a packaging error.
I don’t have packagekit synced to my system - I have no issues with print-manager.
There is not many packages specifically requiring packagekit
$ pacman -Sii packagekit
Repository : extra
Name : packagekit
Version : 1.3.1-1
Description : A system designed to make installation and updates of packages easier
Architecture : x86_64
URL : https://www.freedesktop.org/software/PackageKit/
Licenses : GPL-2.0-or-later
Groups : None
Provides : None
Depends On : libpackagekit-glib pacman libalpm.so=15-64 polkit sqlite
Optional Deps : bash-completion: command completion in bash
Required By : cockpit-packagekit gnome-packagekit packagekit-qt5 packagekit-qt6
Optional For : cosmic-store enlightenment
Conflicts With : None
Replaces : None
Download Size : 521,73 KiB
Installed Size : 2734,54 KiB
Packager : Christian Hesse <eworm@archlinux.org>
Build Date : man 05 maj 2025 19:03:39 CEST
MD5 Sum : eeb48b9206084da97b5686ceb91accea
SHA-256 Sum : a3fd778f385112da6a098dce6c45e4f9b88f37666cb23154e714df6026238095
Signatures : 6D42BDD116E0068F
Extended Data : None
I am unlisting the topic as it appears be a punch in the dark and may throw other readers off track.
@clarkb please provide more information - especially why this specific action solved your issue
1 Like
Ah, but you’re on the Unstable branch, with Plasma 6.4. We are on the Stable branch, with Plasma 6.3.6.
In that case - you will just have to wait until 6.4 hits the fan.
Well, it’s not a problem for myself as I don’t have any printers connected to this machine, but it’s rather unfortunate for those who do, especially since the error message throws up the suggestion that one should install packagekit in order to remedy the problem.
I understand that - I often forget that I am using unstable branch - which makes it rather difficult to reproduce many issues.
1 Like
Just for the record, this may be an interesting exception because Arch (and Manjaro unstable) went directly from 6.3.5 to 6.4.0. print-manager 6.3.6 is built by Manjaro.
Packager : Manjaro Build Server <build@manjaro.org>
1 Like
Interesting indeed. There have been a few more such anomalies in recent times.
Between the previous Stable Update and the most recent one, we Plasma users had ksystemstats 6.4.0 on our machines, and the most recent update changed this — or at least, if you used -Syuu — to 6.3.6.
And then there was that whole business with kwallet and ksecretsd, which was not supposed to have been included in the (previous) update yet.
1 Like
Yes sorry, the kcm 
It needs -DSCP_INSTALL=off in config. CMakeLists.txt · master · Plasma / Print Manager · GitLab
Build CI installs packages not in a clean chroot.
1 Like
Fixed with print-manager 1:6.3.6-2 coming along shortly.
3 Likes
The irony indeed. 
Folks, to be clear: When packages are built together in the same environment, sometimes things can be missed.
Package Maintainers–no matter the distro–make mistakes just like everyone else. 
The only reason why the issue was resolved was due to feedback from users here on the forum. Thank you!
6 Likes