Bug 555014

Summary: Available updates are not visible
Product: [Fedora] Fedora Reporter: Martin Kho <rh-bugzilla>
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, martin.nad89, rdieter, richard, smparrish
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-27 15:12:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 539278    

Description Martin Kho 2010-01-13 12:39:36 UTC
Description of problem:
In kpackagekit - stand alone and system settings - available updates are not visible in the Updates Software window. When pressing the "Select all Updates" button install the updates.

Version-Release number of selected component (if applicable):
kpackagekit-0.6.0-0.1.20100111.fc13.x86_64
PackageKit-0.6.0-1.fc13.x86_64

How reproducible:
1. Check that there are updates available (yum check-updates)
2. Start Add and Remove Software (System Settings) or KPackagekit stand alone
3. Go to Software Updates
N.B. Refresh refreshes the list, but again available updates are not shown 
  
Actual results:
Updates are not visible in Software Updates window

Expected results:
Updates are visible in Software Updates window

Additional info:

Comment 1 Rex Dieter 2010-01-13 13:55:44 UTC
I can confirm I've experienced this as well (mostly on fc12)

Comment 2 Martin Naď 2010-01-23 21:40:48 UTC
*** Bug 558142 has been marked as a duplicate of this bug. ***

Comment 3 Martin Naď 2010-01-25 18:22:33 UTC
new kpackagekit-0.5.4-2.fc12.x86_64 fix problem in comment 2

Comment 4 Kevin Kofler 2010-02-09 15:24:00 UTC
Is this still happening on F13?

Comment 5 Martin Kho 2010-02-09 16:00:07 UTC
Yes ;-( Comment 3 has to do with F12. In rawhide I still have version 0.6.0-0.1.20100111.fc13.x86_64 for kpackagekit and PackageKit version 0.6.1-1.fc13.x86_64.

Martin Kho

Comment 6 Martin Naď 2010-02-26 15:11:26 UTC
with kpackagekit-0.6.0-0.5.r1095080.fc13.i686
     PackageKit-0.6.2-0.1.20100225git.fc13.i686
still this

this paste to console:
KPackageKit(20126): ""CurrencyIntroducedDate" - conversion of "" to QDate failed" " (wrong format: expected 3 items, got 1)" 
KPackageKit(20126): ""CurrencyIntroducedDate" - conversion of "" to QDate failed" " (wrong format: expected 3 items, got 1)" 
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Object::connect: No such signal PackageKit::Transaction::package(PackageKit::Package *)

Comment 7 Kevin Kofler 2010-02-26 16:37:44 UTC
PackageKit-0.6.2-0.1.20100225git.fc13.i686 need yet another new kpackagekit snapshot, r1095080 was for the previous PackageKit snapshot. PackageKit-qt 0.6 has a very unstable API.

Comment 9 Martin Naď 2010-02-27 15:07:28 UTC
kpackagekit-0.6.0-0.6.20100223svn.fc13 work ok show updates/aviables packages.

[martin@localhost ~]$ kpackagekit 
KPackageKit(1934): ""CurrencyIntroducedDate" - conversion of "" to QDate failed" " (wrong format: expected 3 items, got 1)" 
KPackageKit(1934): ""CurrencyIntroducedDate" - conversion of "" to QDate failed" " (wrong format: expected 3 items, got 1)" 
[martin@localhost ~]$ Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Error, cannot create transaction proxy
QDBusConnection: name 'org.freedesktop.PackageKit' had owner '' but we thought it was ':1.52'
enumFromString ( Info ) : converted "" to "UnknownInfo" , enum value 0 
enumFromString ( Info ) : converted "" to "UnknownInfo" , enum value 0

Comment 10 Kevin Kofler 2010-02-27 15:12:37 UTC
OK, so the new KPackageKit fixes that, closing as a duplicate.

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