Bug 949342

Summary: gnome-packagekit does not work at all
Product: [Fedora] Fedora Reporter: drago01
Component: gnome-packagekitAssignee: Richard Hughes <rhughes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: nsoranzo, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-08 15:24:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
verbose output none

Description drago01 2013-04-07 22:00:27 UTC
Created attachment 732457 [details]
verbose output

Description of problem:

When trying to use gpk-update-viewer to install upgrades it does nothing which means it shows me which packages needs to be updated. After clicking on the update button it asks me for additional deps to install and then sits there showing the main window.

The gpk-update-viewer uses 97% cpu but the yum backend does not seem to do anything at all.

Updating with yum works fine (I have attached the verbose output to this bug).

Version-Release number of selected component (if applicable):
gnome-packagekit-3.6.2-1.fc18.x86_64
PackageKit-0.8.7-1.fc18.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open gpk-update-viewer
2. Try to install updates
  
Actual results:

It does not install updates and does not show any error message either.
yum works fine.

Expected results:
Install the updates.

Additional info:

Verbose log is attached. 
It says:
23:54:06	GnomePackageKit	status update
23:54:06	GnomePackageKit	status cleanup

multiple times (and shows the cleanup icon for the packages) even though it did not do anything with them.

Comment 1 Nicola Soranzo 2013-04-08 15:24:05 UTC

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