Bug 951804 - gpk-update-viewer often refuses to do anything
Summary: gpk-update-viewer often refuses to do anything
Keywords:
Status: CLOSED DUPLICATE of bug 909761
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-packagekit
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-13 09:12 UTC by Pierre Ossman
Modified: 2013-06-27 13:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-27 13:53:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.