Hide Forgot
Created attachment 542052 [details] gpk screenshot Description of problem: After updating a set of packages that included a package that required a reboot, I was presented with a prompt to restart my computer. The window's buttons do not respond to clicking and I noticed the app had entered an infinite loop. I will attach a screenshot. Version-Release number of selected component (if applicable): PackageKit-0.6.20-1.fc16.x86_64 yum-3.4.3-5.fc16.noarch gnome-packagekit-3.2.1-1.fc16.x86_64 How reproducible: I had this happen to me on another machine yesterday but I did not capture a screenshot or any other information. Steps to Reproduce: Update a package that has the reboot flag turned on. Actual results: Frozen update window. Expected results: Clickable buttons that reboot my computer.
The same thing just happened on yet another machine. The same group of packages were updated so that it required a restart. The restart window is displayed but the buttons do not respond to clicks. The gpk-update-viewer process is using 99%+ CPU time. The same version of PackageKit, yum, and gnome-packagekit are installed on the third machine to exhibit this bug.
It happened again today. It seems to be correlated to when kernel updates are released. Running updates that do not include the kernel do not cause gpk-update-viewer to under an infinite loop. Does gpk-update-viewer do something special for the kernel?
My guess seems to be correct. Updated on a different machine with the kernel checked and other updates unchecked and it froze on me at the "You must restart" prompt. Other updates that require a log-out or restart do not freeze gpk-update-viewer. Why is the kernel special?
It happened today but it was asking for me to log out. I had to kill -6 the gpk-viewer process. I had selected about 25 of 30 updates (no kernel updates).
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.