Description of problem: - fresh F13 install (installed from NFS sources, as additional repos was specified fedora-updates and rpmfusion-{,non}free{,-updates} ) - run "Software Update" tool. It found 4 updates (gdisk from updates, dvd95/traverso/vobcopy from rpmfusion-free-updates) - click "Install Updates", updates are downloaded, dependencies resolved etc. - "Software signature is required" window appears with title "Do you trust the source of the package" for dvd95-1.6p0-2.fc13.i686 from rpmfusion-free-updates. - "Authenticate:" "Authentication is required to consider a key used for signing packages as trusted" window appears, I enter root password and click "Authenticate". - Ack "Do you recognise the user and thust this key" and appears error window "Could not update package", "Failed to process request." "More details:" failed to install signature: Traceback (most recent call last): File "/usr/share/PackageKit/helpers/yum/yumBackend.py", line 2926, in install_signature self.yumbase.getKeyForPackage(pkg, askcb = lambda x, y, z: True) File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 4329, in getKeyForPackage result = ts.pgpImportPubkey(misc.procgpgkey(info['raw_key'])) File "/usr/lib/python2.6/site-packages/rpmUtils/transaction.py", line 59, in __getattr__ return self.getMethod(attr) File "/usr/lib/python2.6/site-packages/rpmUtils/transaction.py", line 69, in getMethod return getattr(self.ts, method) AttributeError: 'NoneType' object has no attribute 'pgpImportPubkey' - when I "yum update vobcopy gdisk", yum rightly prompt for and import GPG key for these (fedora-updates and rpmfusion-free-updates) repos and then update packages. - subsequent "Software Update" tool run will rightly find outstanding two updates and install them. Version-Release number of selected component (if applicable): gnome-packagekit-2.30.3-1.fc13.i686 PackageKit-0.6.6-1.fc13.i686 Additional info: PackageKit (or gnome-packagekit) probably expect, that GPG keys are already imported and crashes when not. YUM behaves correctly.
*** This bug has been marked as a duplicate of bug 622179 ***