Bug 922697

Summary: gpk-update-viewer hangs with 100% CPU after displaying "installing updates"
Product: [Fedora] Fedora Reporter: Martin Wilck <martin.wilck>
Component: gnome-packagekitAssignee: Richard Hughes <rhughes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 18CC: chorn, hugh, jan.public, line72, mbuckley001, nsoranzo, pawsa, pwouters, rhughes, root
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 14:58:23 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
screenshot of gpk-update-viewer in error situation none

Description Martin Wilck 2013-03-18 10:18:40 UTC
Created attachment 711852 [details]
screenshot of gpk-update-viewer in error situation

Description of problem:
gpk-update-viewer hangs with 100% CPU after displaying "installing updates"

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

How reproducible:
always

Steps to Reproduce:
1. Software-> Check for updates -> (list of updates displayed) -> install
  
Actual results:
"Checking dependencies" ... "Installing updates" ,,,
Nothing happens any more gpk-update-viewer shows with 100% CPU in "top"
Updates are not installed (same thing will happen next time gpk-update-viewer ist started).


Expected results:
Update installation finishes, or error message is displayed

Additional info:
The packagekit logs ("Software->Software Log") show a list of packages of which packagekit thinks they were installed, but these packages were never actually installed.

This system is not a fresh installation, it had been updated from F17 using Fedup.

Comment 1 Martin Wilck 2013-03-18 10:22:31 UTC
I created a core dump of gpk-

Comment 2 Martin Wilck 2013-03-18 10:24:43 UTC
I have a 27MB core file of gpk-package-viewer created with gcore(*) on 
ftp://ftp.ts.fujitsu.com/outgoing/core.17275.xz. Please download quickly, it will be purged after a few days.

Comment 3 Jan Vlug 2013-03-20 18:45:26 UTC
Duplicate of: bug #830365 ?

Comment 4 Martin Wilck 2013-03-21 08:14:44 UTC
Well, I'm not using Apper. I am running GNOME here, Apper isn't even installed. I am certain I never saw the issue under F17. 

Should I run pkmon? If yes, with what options?

Comment 5 Erik Ekman 2013-03-27 17:45:49 UTC
This happens to me as well, but with gnome-packagekit-3.6.2-1.fc18.x86_64

Comment 6 Paul Wouters 2013-03-29 02:17:43 UTC
I hit this one too. strace shows it is looping of stat()ing a file:


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, 0x151b784, 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)
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) = 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
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) = 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


This file comes from  gnome-packagekit-3.6.1-2.fc18.x86_64, could this be a weird case of recursion on updating one of its own files?

Comment 7 M D 2013-04-01 14:09:57 UTC
I have the same issue with gnome-packagekit-3.6.2-1.fc18.x86_64. strace shows the same output as Paul's. I've let it run for well over an hour and strace is still showing the same output.

Comment 8 Michael Buckley 2013-04-02 19:21:29 UTC
I have the same issue with the gpk-update-viewer reaching 96% cpu and no update activity.  I am running:

Release 18 (Spherical Cow) 64-bit
Kernel Linux 3.8.3-201.fc18.x86_64
GNOME 3.6.2

Does anyone have a workaround?  I am now about 157 updates behind times ....

Comment 9 Erik Ekman 2013-04-02 20:46:14 UTC
'yum update' still works.

Comment 10 Martin Wilck 2013-04-03 08:43:32 UTC
(In reply to comment #9)
> 'yum update' still works.

It sure does. But I have been keeping this system state for several weeks now because I want to be able to reproduce the problem, just in case someone starts to try and fix the problem.

Comment 11 Martin Wilck 2013-04-03 08:50:44 UTC
(In reply to comment #2)
> I have a 27MB core file of gpk-package-viewer created with gcore(*) on 
> ftp://ftp.ts.fujitsu.com/outgoing/core.17275.xz. Please download quickly, it
> will be purged after a few days.

I have just uploaded the core file again.

Comment 12 Michael Buckley 2013-04-03 14:03:47 UTC
Thank you for the workaround.

Comment 13 Nicola Soranzo 2013-04-08 14:58:23 UTC

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