Description of problem: After asking PackageKit to install a bunch of things, packagekit brought up a box that said: """ Method "InstallPackages" with signature "as" on interface "org.freedesktop.PackageKit.Transaction" doesn't exist """ Version-Release number of selected component (if applicable): % yum list installed '*packagekit*' Installed Packages PackageKit.x86_64 0.3.6-2.fc10 installed PackageKit-libs.x86_64 0.3.6-2.fc10 installed PackageKit-udev-helper.x86_64 0.3.6-2.fc10 installed PackageKit-yum.x86_64 0.3.6-2.fc10 installed PackageKit-yum-plugin.x86_64 0.3.6-2.fc10 installed gnome-packagekit.x86_64 0.3.6-2.fc10 installed
The above probably requires a lot of s/packagekit/gnome-packagekit/ as it was from gpk-application ... but I assume the problem is not gnome-packagekit specific.
EEek. That looks like the daemon crashed. Could you try reproducing with /usr/sbin/packagekitd under gdb please? Thanks.
I can duplicate the same problem when using the plugin installer helper. 1. use totem to try to play a file without a codec. 2. click "Search" to locate plugin 3. it finds gstreamer-plugins-bad 4. click to install 5. enter authorization details 6. comes up with "Installing Packages" progress bar 7. suddenly halts with a "Failed to install package" with the following in the details: Method "InstallPackages" with signature "as" on interface "org.freedesktop.PackageKit.Transaction" doesn't exist $ rpm -q PackageKit PackageKit-0.3.6-3.fc10.i386
It works for me, but it's good it's reproducable as I can give you some more instructions :-) Can you (as root) do: killall packagekitd /usr/sbin/packagekitd --verbose --disable-timer and then try to reproduce the crash? You should have a metric ton of debugging output, please can you save it _all_ and attach it to this bug. Hopefully (?!) the daemon crashes, and we see what it was doing. Thanks.
Next time I tried doing it (after a reboot) it worked as advertised. Reproducing it could be a little tricky, but if it comes up again, I'll try the debugging steps.
Okay, thanks.
*** This bug has been marked as a duplicate of bug 469950 ***