Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 77892 - Alert Notification Tool configuration dialogs contain mislabeled buttons
Alert Notification Tool configuration dialogs contain mislabeled buttons
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhn-applet (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Daniel Veillard
Red Hat Satellite QA List
Depends On:
  Show dependency treegraph
Reported: 2002-11-14 16:40 EST by Need Real Name
Modified: 2007-11-30 17:07 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-09-28 16:21:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-11-14 16:40:58 EST
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux) 
Description of problem: 
When run under KDE, two of the "Red Hat Network Alert Notification Tool" 
configuration dialog boxes contain misleading instructions.  The first dialog 
prompts the user to "Click 'Next' below to begin configuration," when the only 
options are "Cancel," "Back," and "Forward."  The final dialog in the 
configuration process prompts the user to "Click 'Finish' below" when the only 
options are "Cancel," "Back," and "Apply."  
Version-Release number of selected component (if applicable): 2.0.0 
How reproducible: 
Steps to Reproduce: 
1. Run KDE. 
2. Right-click on the Alert Notification Tool icon on the panel 
   and select "Configuration." 
3. Page through the four configuration dialogs.  Notice the 1st 
   and 4th contain text that misidentifies the available buttons.	 
Additional info:
Comment 1 Daniel Veillard 2003-09-28 16:21:17 EDT
Both messages have been updated to reflect the button labels so this 
should be fixed in the current version,



Note You need to log in before you can comment on or make changes to this bug.