Red Hat Bugzilla – Bug 466290
Add/Remove Software fails on it's first action
Last modified: 2008-11-06 05:58:53 EST
Description of problem:
The first time you hit apply after marking or unmarking packages for instalation or removal in 'Add/Remove Programs' the action fails out with an 'unknown error'. The details are:
Method "InstallPackages" with signature "as" on interface "org.freedesktop.PackageKit.Transaction" doesn't exist
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Clean install of FC10 beta, gnome desktop, apply all updates as of 11:32am EST 10/9/08
2. Open Add/Remove Software
3. In the 'Games' category, select 'apricots'
4. Click 'Apply'
5. A new dialog box will pop up, showing progress...
6. Authenticate when asked
7. A new dialog box will pop up with the error message, close it and the prior progress dialog box.
8. Click 'Apply' again, the progress dialog box will appear, the install will go through cleanly, and you'll be asked if you want to run your new app. Any further install/uninstall actions will proceed normally as long as you don't restart Add/Remove Software.
First install/uninstall fails, all after proceed normally
First install/uninstall should work without error
Doesn't seem to matter if the first install/uninstall pulls in additional packages for changes, or if you select multiple for the first action.
I think I've found the bug in PkControl, I'll commit this upstream, then roll a package.
When the new packages have built in http://koji.fedoraproject.org/koji/taskinfo?taskID=871330 -- can you try those please. Thanks.
I upgraded to PackageKit-0.3.6-3.fc10.i386 using the rpm's you linked to, still getting the same behavior and error.
I can not reproduce the error after updating this afternoon. I see I'm now running PackageKit-0.3.7-1.fc10.i386
Gah, I marked this bug as closed too quickly, just ran into it again trying to install Audacious.
I get the same error using PackageKit-0.3.8-2.fc10.i386 on Fedora 10 beta (184.108.40.206-34.rc1.fc10.i686, all updates applied).
*** This bug has been marked as a duplicate of bug 469950 ***