Bug 951804

Summary:	gpk-update-viewer often refuses to do anything
Product:	[Fedora] Fedora	Reporter:	Pierre Ossman <pierre-bugzilla>
Component:	gnome-packagekit	Assignee:	Richard Hughes <rhughes>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	danny, 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-06-27 13:53:49 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:

Description Pierre Ossman 2013-04-13 09:12:37 UTC

Description of problem:
When I get the notification that system updates are available, and gpk-update-viewer is launched, it will often simply not work. Pressing "Install updates" does a few things, and then the process stops. "Install updates" is now disabled and the only way to try again is to restart gpk-update-viewer.


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


How reproducible:
80%


Steps to Reproduce:
1. Start gpk-update-viewer
2. Press Install Updates
  

Actual results:
It stops mid-process.


Expected results:
Updates are installed.


Additional info:

Comment 1 Danny Staple 2013-05-31 11:51:58 UTC

I've been able to use sudo yum update manually to sidestep this - but I am also experiencing this on FC18 x86_64 too.

If I use sudo to run gpk-update-viewer, it mentions what it will need to do (further than without the sudo), but then does nothing and needs a restart.

This is currently 100% reproducible for me. 
I can confirm it is the same version as above.

Comment 2 Danny Staple 2013-05-31 11:58:50 UTC

Pierre, I am going to try checking top (or process monitor) when I next see this - it may be a duplicate of #909761. If we can prove it - then we should add our names to the CC list there and close this as a dupe.

Comment 3 Pierre Ossman 2013-06-04 10:31:35 UTC

Happened again today, and top shows it eating 100% CPU. So it could be a dupe.

Comment 4 Danny Staple 2013-06-10 12:57:21 UTC

I have 100% cpu too. I think is definitely a duplicate. I don't think I can set the status though.

Comment 5 Nicola Soranzo 2013-06-27 13:53:49 UTC


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