Ubuntu uses python-aptdaemon.pkcompat by default instead; it bridges PackageKit interfaces into much more modern AptDaemon. See https://launchpad.net/aptdaemon for advantages over packagekit-backend-aptcc
So it seems that that's a bug in python-aptdaemon.pkcompat now.
Ubuntu uses python- aptdaemon. pkcompat by default instead; it bridges PackageKit interfaces into much more modern AptDaemon. See https:/ /launchpad. net/aptdaemon for advantages over packagekit- backend- aptcc
So it seems that that's a bug in python- aptdaemon. pkcompat now.