Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 7816 - GUI text field doesn't always accept input.
GUI text field doesn't always accept input.
Product: Red Hat Linux
Classification: Retired
Component: usermode (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 1999-12-15 13:47 EST by apeacock
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-13 17:40:30 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 apeacock 1999-12-15 13:47:54 EST
Close to 50% of the time, I can't enter a password as a regular user after
selecting "halt" or "reboot" from the Gnome logout.  This appears to be a
problem with userhelper or the underlying widgets used when running
userhelper in graphical mode.

The interesting thing is that the buttons ("ok" and "cancel") *do* accept
input from the mouse, but the text box simply will not get an activated
cursor nor will any text (or *'s) appear as I type.

This is an erratic problem, and I haven't been able to isolate what
differeneces exist between times when it does work and times when it does

The problem also existed in RH6.0.
Comment 1 Michael K. Johnson 1999-12-15 15:20:59 EST
I expect that it is caused by something relatively unusual in your
environment, since this is the first I've heard of it.

I'll start out with the obvious questions...

Are you using the default Enlightenment window manager, or have you
changed it to something else?
Comment 2 Nalin Dahyabhai 2000-01-13 17:40:59 EST
This should be fixed in usermode-1.19, which will be in the next version
of Raw Hide.  Please reopen this bug if you continue to have problems
after an upgrade.

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