Bug 911915 - gpk-update-viewer seems to get stuck
Summary: gpk-update-viewer seems to get stuck
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-02-16 17:50 UTC by Jim Haynes
Modified: 2013-04-08 14:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-08 14:57:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jim Haynes 2013-02-16 17:50:16 UTC
Description of problem:Checking for updates, the program seems to get stuck


Version-Release number of selected component (if applicable):
gnu-packagekit 3.6.1-2.fc18.i686

How reproducible:Not very - happens now and then


Steps to Reproduce:
1.applications->system tools->software and click on software->check for updates
2.wait
3.wait
  
Actual results:Displayed that it was checking for updates, after about 20
minutes it showed a lit of a few updates, on clicking on install updates
it displays downloading update information again for a long time with no
apparent progress


Expected results: Display updates, if any, promptly and install them
promptly


Additional info:
I'm looking at the contents of /var/cache/yum/i686/18/updates
The file updateinfo.xml.gz grows with time, then gets smaller and
starts growing again (as if it is being downloaded over and over)
At first the only process running was gpk-update-viewer
After the list of updates showed up and I clicked on install updates
that process is running and also a great long thing involving python
Quit and restart and the same thing was happening.

When I got tired of waiting I quit the GUI and ran yum update.  It
proceeded normally, and produced a much larger list of updates than
the GUI had done.  And installed them with no error messages and no
delays.

Comment 1 prudy 2013-03-17 15:53:34 UTC
I'd like to confirm this behaviour. If you monitor the network transfer it constantly jumps to the new server getting the file over and over.

Comment 2 Russell Harrison 2013-03-23 17:43:23 UTC
I'm also running into the same issue on F18.  I did a strace of the process to see if I could figure out why it was using so much cpu and found it trying to access the same file over and over again.

lstat("/usr/share/gnome-packagekit/icons/hicolor/22x22/status/pk-package-installed.png", {st_mode=S_IFREG|0644, st_size=695, ...}) = 0
open("/usr/share/gnome-packagekit/icons/hicolor/22x22/status/pk-package-installed.png", O_RDONLY|O_NOATIME) = -1 EPERM (Operation not permitted)
open("/usr/share/gnome-packagekit/icons/hicolor/22x22/status/pk-package-installed.png", O_RDONLY) = 13
read(13, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\0\26\0\0\0\26\10\6\0\0\0\304\264l"..., 4096) = 695
close(13)                               = 0
open("/usr/share/gnome-packagekit/icons/hicolor/22x22/status/pk-package-installed.png", O_RDONLY) = 13
fstat(13, {st_mode=S_IFREG|0644, st_size=695, ...}) = 0
read(13, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\0\26\0\0\0\26\10\6\0\0\0\304\264l"..., 65536) = 695
read(13, "", 65536)                     = 0
close(13)                               = 0
recvfrom(6, 0x7d0d74, 4096, 0, 0, 0)    = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=3, events=POLLIN}], 3, 0) = 0 (Timeout)
recvfrom(6, 0x7d0d74, 4096, 0, 0, 0)    = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=3, events=POLLIN}], 3, 0) = 0 (Timeout)
recvfrom(6, 0x7d0d74, 4096, 0, 0, 0)    = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=3, events=POLLIN}], 3, 0) = 0 (Timeout)

Comment 3 Nicola Soranzo 2013-04-08 14:57:47 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.