Hide Forgot
Description of problem: Software Update applet is getting list updates each 5 seconds. This makes him completely unusable. Version-Release number of selected component (if applicable): $ rpm -qa PackageKit* PackageKit-glib-0.5.8-8.el6.x86_64 PackageKit-gtk-module-0.5.8-8.el6.x86_64 PackageKit-0.5.8-8.el6.x86_64 PackageKit-gstreamer-plugin-0.5.8-8.el6.x86_64 PackageKit-yum-plugin-0.5.8-8.el6.x86_64 PackageKit-yum-0.5.8-8.el6.x86_64 PackageKit-device-rebind-0.5.8-8.el6.x86_64 How reproducible: Steps to Reproduce: 1. Login to gnome 2. Click on the orange "star-like" icon placed on gnome-panel signalizing that updates are available Actual results: Dialog gets refreshed every 5 seconds. This makes him completely unusable Expected results: Update applet should get list of updates in reasonable interval.
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. **
Could you please get the output of: killall gpk-update-icon gpk-update-icon --verbose and attach it to this bug. The only reason the update viewer is meant to self-refresh is: a) when the network state changes b) when the number of updates changes (i.e. the user does yum update on the command line) c) any of the repos changes enabled state So I'm kinda confused which of those are causing the 5 second refresh. Thanks.
Created attachment 435301 [details] gpk-viewer --verbose
Created attachment 435303 [details] pkmon --verbose pkmon --verbose after gpk-update-viewer)
Could you try the build here please: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2645366 You'll need to restart after installing the update.
Verified on PackageKit*.0.5.8.9.el6
Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.