Red Hat Bugzilla – Bug 169677
Deselecting any package disables FORWARD button
Last modified: 2013-01-10 03:48:46 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.7.12-188.8.131.52
Description of problem:
After 'checking/clicking' the 'select all packages' checkbox, deselecting any package disables the FORWARD button, requiring you to deselect and then reselect some other package, as selecting a package re-enables the button.
As I am running a latter version of spamassassin than the one in the channel, I must always deselect it after clicking on the 'select all packages' check-box. This disables the forward button. Previous version did not do this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch up2date.
2. Click 'select all packages' or whatever its called.
3. Deselect something on the list.
4. Observer that the button is disabled even though there may be 100 other packages to get.
Actual Results: Button disabled.
Expected Results: Button should be enabled if there are packages in the list to fetch.
Previous version was OK.
I think this was added in FC4, because FC3 or FC2 didn't do this. Some
programmer probabaly thought it would be clever to have the forward button
disabled if "all" the packages are supposed to be installed but one of them is
unchecked. . . Except this is very annoying, because the only way it got
unchecked is the user unchecked it. And the only other way to check the 99 other
packages is one at a time. Please turn this into a real "Select All"/"Unselect
All" button, or at least restore old behavior.
This seems to be fixed by an update through the channel, version up2date-4.4.67-3.
Blocking rhnupr4u4 and rhnupr3u8 to track the progress of the release
Moving bugs to the CanFix List
Current version up2date-4.4.67-3 does not suffer from this problem.
Should be marked are ERRATA?
This is fixed in at least release 4.4.67-4
This bug did not make the code freeze and it will not be fiixed during this
release cycle. Re-aligning bug to the next release
This bug did not make the code freeze. It will not be fixed in this releasee
Reea ligning to the next one.