Bug 75650 - xscreensaver-demo Pop up help baloons have same message for all text boxes with different uses.
xscreensaver-demo Pop up help baloons have same message for all text boxes wi...
Status: CLOSED DUPLICATE of bug 78491
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2002-10-10 13:10 EDT by Jesse Keating
Modified: 2014-03-16 22:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:49:52 EST
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 Jesse Keating 2002-10-10 13:10:20 EDT
Description of problem:
In xscreensaver-demo, there are 3 text boxes, one for "Blank After:", one for
"Cycle After:", and one for "Lock Screen After:".  If you hover the mouse in the
text feild, a popup help baloon shows up.  For each of hte 3 boxes, the same
baloon comes up stating:  "How long before the monitor goes completely black."

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

How reproducible:

Steps to Reproduce:
1. Launch xscreensaver-demo
2. check the "Lock screen after" checkbox
3. Hover mouse over all 3 of the text boxes, long enough to get the popup help

Actual Results:  All 3 baloons say the same thing.

Expected Results:  Each baloon would match the function of the box.

Additional info:

I use xscreensaver-demo because I don't use either KDE or GNOME, and I don't
want to launch a KDE or GNOME control panel tool to alter screensaver settings.
Comment 1 Bill Nottingham 2003-02-06 17:46:02 EST

*** This bug has been marked as a duplicate of 78491 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:49:52 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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