Summary: | Error when i update a list of packages or only one | ||
---|---|---|---|
Product: | [Unmaintained] kpackagekit | Reporter: | Patricio Paiva <ppaiva> |
Component: | general | Assignee: | Steven M. Parrish <smparrish> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, dantti12 |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patricio Paiva
2009-07-02 23:10:22 UTC
Looks like the problem is with PolicyKit, can you try doing the same with gnome-packagekit? Thanks. and The version of KPackageKit, pacakgekit-qt and PAckageKit helps a lot. Hi. Sorry, but in my PC i have KDE (not GNOME). Just for information: i read the list of package of the application KPackageKit, then i take the name of the first package in the window list... then (in a console window) execute "yum install" command with the name of package (taken from de application) and the command is ok. I hope that comment help... Thank's. Hi. Any idea for this bug??.... Thank's in advance. Atte Patricio Paiva Well It's a bit complicated to get the idea of why this is happening since the error seems to happen in PolicyKit code so let's try looking at versions rpm -qa |grep -i packagekit rpm -qa |grep -i policykit rpm -qa |grep -i polkit Hi. The output is: rpm -qa |grep -i packagekit PackageKit-yum-0.4.8-1.fc11.i586 PackageKit-yum-plugin-0.4.8-1.fc11.i586 PackageKit-glib-0.4.8-1.fc11.i586 gnome-packagekit-2.27.2-1.fc11.i586 kpackagekit-0.4.1.1-1.fc11.i586 PackageKit-gstreamer-plugin-0.4.8-1.fc11.i586 PackageKit-0.4.8-1.fc11.i586 PackageKit-gtk-module-0.4.8-1.fc11.i586 PackageKit-qt-0.4.8-1.fc11.i586 rpm -qa |grep -i policykit PolicyKit-gnome-libs-0.9.2-3.fc11.i586 PolicyKit-kde-4.2.90-1.fc11.i586 PolicyKit-0.9-6.fc11.i586 rpm -qa |grep -i polkit polkit-qt-0.9.2-1.fc11.i586 Thank's Atte Patricio Paiva. This could be related to bug 218200. Thanks *** This bug has been marked as a duplicate of bug 218200 *** |