Bug 170065

Summary:	up2date "forward" button disabled if packages selected via spacebar
Product:	Red Hat Enterprise Linux 3	Reporter:	Adrian Likins <alikins>
Component:	up2date	Assignee:	Adrian Likins <alikins>
Status:	CLOSED ERRATA	QA Contact:	Beth Nackashi <bnackash>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.0	CC:	jfrieben, suvi
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2006-0105	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-03-15 15:36:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	164824, 168424, 169775

Description Adrian Likins 2005-10-06 22:32:56 UTC

+++ This bug was initially created as a clone of Bug #166034 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050524
Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
If when you're on the screen where you selected which packages you want to
download and install (this screen has "all packages" at the top or you can
select individually which ones you want) and you highlight a package and press
the spacebar (which checks that package) the "forward" button disables itself. 
You have to use the mouse to physically uncheck and then recheck the package.

Version-Release number of selected component (if applicable):
up2date-4.4.23-4

How reproducible:
Always

Steps to Reproduce:
1.Run up2date GUI
2.Let it 
3. Get to where you select the packages and then try to highlight one and then
press the spacebar to select it.  You will see "forward" button does NOT enable
itself as it should
  

Actual Results:  "forward" button does NOT enable itself as it should

Expected Results:  "forward" button should have enabled itself

Additional info:

-- Additional comment from petrosyan on 2005-08-16 20:05 EST --
this is a duplicate of bug #158396

-- Additional comment from petrosyan on 2005-09-17 17:36 EST --
*** Bug 158396 has been marked as a duplicate of this bug. ***

-- Additional comment from alikins on 2005-10-06 17:02 EST --
this should be fixed in up2date-4.4.51

Comment 2 Debbie McGrath 2005-10-19 15:03:14 UTC

Mistakenly removed from the RHEL3U7Proposed list.
Just putting it back.

Comment 3 Debbie McGrath 2005-10-19 15:04:34 UTC

Actually, already has the required ACKs.
Moving to RHEL3U7CanFix and rhnupr3u7-must.

Comment 7 Beth Nackashi 2005-12-14 17:17:15 UTC

verified on i386, ia64, and x86_64 with up2date-4.4.56-3

Comment 9 Red Hat Bugzilla 2006-03-15 15:36:44 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0105.html