Bug 558142

Summary: kpackage not show updates/available packages
Product: [Fedora] Fedora Reporter: Martin Naď <martin.nad89>
Component: kpackagekitAssignee: Steven M. Parrish <smparrish>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: balajig81, kevin, ltinkl, rdieter, richard, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-23 21:40:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Naď 2010-01-23 21:39:42 UTC 
Description of problem:
kpackagekit not show  updates/available packages

Version-Release number of selected component (if applicable):
kpackagekit-0.5.4-1.fc12.x86_64
kpackagekit-0.5.2-3.fc12

How reproducible:
everytime

Steps to Reproduce:
1.
2.
3.
  
Actual results:
kpackagekit not show  updates/available packages

Expected results:
kpackagekit show updates/available packages

Additional info:
this paste to konsole:
[namar@fedora ~]$ kpackagekit
[namar@fedora ~]$ removing transaction from pool :  "/57_bcedacad_data"
removing transaction from pool :  "/58_bdbaecee_data"
removing transaction from pool :  "/59_caadaeee_data"
removing transaction from pool :  "/60_bbccccae_data"
removing transaction from pool :  "/61_acccabcb_data"
removing transaction from pool :  "/62_acacbcca_data"
removing transaction from pool :  "/63_babaeade_data"
removing transaction from pool :  "/64_addaddec_data"
enumFromString ( State ) : converted "" to "UnknownState" , enum value 0
removing transaction from pool :  "/65_eeeddbca_data"
removing transaction from pool :  "/66_cbbdaaac_data"
removing transaction from pool :  "/67_adeeadbe_data"
Comment 1 Martin Naď 2010-01-23 21:40:48 UTC 

*** This bug has been marked as a duplicate of bug 555014 ***