Sorry, on my system there was for some reason, perhaps some experiments several months ago, installed the original PackageKit D-Bus service ("packagekit" binary package) and not the Ubuntu standard PackageKit D-Bus service emulation using aptdaemon ("python3-aptdaemon.pkcompat" binary package). aptdaemon was installed, giving me the impression that it was used.
This caused the bug to occur and after returning to the standard setup with python3-aptdaemon.pkcompat the bug went away.
So the bug is most probably in the packagekit package and most users are stillhaving automatic printer driver installation working, so moving to packagekit and lowering importance ...
Sorry, on my system there was for some reason, perhaps some experiments several months ago, installed the original PackageKit D-Bus service ("packagekit" binary package) and not the Ubuntu standard PackageKit D-Bus service emulation using aptdaemon ("python3- aptdaemon. pkcompat" binary package). aptdaemon was installed, giving me the impression that it was used.
This caused the bug to occur and after returning to the standard setup with python3- aptdaemon. pkcompat the bug went away.
So the bug is most probably in the packagekit package and most users are stillhaving automatic printer driver installation working, so moving to packagekit and lowering importance ...