Description of problem: After yum-3.2.27-1.fc12.noarch update was installed gpk-application (Add/Remove Software) could not do any finds. Version-Release number of selected component (if applicable): PackageKit-0.5.7-1.fc12.x86_64 yum-3.2.27-1.fc12.noarch How reproducible: Very reproducible. This was broken in all machines with current updates. Steps to Reproduce: 1. Update yum to current release. 2. Open Add/Remove Software 3. Enter any known package in the Find box 4. Click Find Actual results: Error popup "An internal system error has occurred" Traceback (most recent call last): File "/usr/share/PackageKit/helpers/yum/yumBackend.py", line 391, in _do_search for (pkg, inst) in res: ValueError: too many values to unpack Expected results: List of matching packaged displayed Additional info: I could find any logs pertaining to this fault. Others have reported this in fedoraforum http://forums.fedoraforum.org/showthread.php?t=242707
Same problem after same update of yum-3.2.27-1.fc12.noarch on Mar 23. As explained in the forum, "yum downgrade yum" is a workaround. The downgrade remove yum.noarch 0:3.2.27-1.fc12 and re-install yum.noarch 0:3.2.27-1.fc12. Finding packages is then workable again with gnome-packagekit.
there is a duplicate bug report filed a few hours earlier: https://bugzilla.redhat.com/show_bug.cgi?id=576451 ps: i also tried a 'yum clean all' just to see, but it didnt help.
update of yum-3.2.27-1 introduced a change in function SearchGenerator in file /usr/lib/python2.6/site-packages/yum/__init__.py where a tuple of 3 items is returned to function _do_search in /usr/share/PackageKit/helpers/yum/yumBackend.py which is still expecting a tuple of only 2 items hence the unpacking error. Adding a variable to line 391 "for (pkg, x, inst) in res:" for example will stop the error and allow the search to continue and display the search results.
I have the same problem with Packagekit.
I tried Jean-Filip Tripcevic's fix and it worked for me with yum-3.2.27-1.fc12.noarch.rpm and, of course, it breaks if I downgrade back to yum-3.2.25-1.fc12.noarch.rpm. Merci Jean-Filip.
*** Bug 577031 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 576169 ***
yum-3.2.27-2.fc12 fixes this problem for me. Please note, if you added the work around in yumBackend.py you will need to remove it when you update to yum-3.2.27-2.fc12 Thank you all.