Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 84233 - OK does not work
Summary: OK does not work
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-users
Version: 8.0
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-13 18:07 UTC by bIRDIE
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-13 19:32:52 UTC


Attachments (Terms of Use)

Description bIRDIE 2003-02-13 18:07:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs-CZ; rv:1.3b) Gecko/20030210

Description of problem:
When I use some national characters in the full user name field (characters like
�,� etc.), OK button doesn't work

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


How reproducible:
Always

Steps to Reproduce:
1. Open redhat-config-users, open some user properties and enter nationas
characters (especially from iso-latin-2 charset) into full user name field.
2. Try to close dialog saving changes

Actual Results:  nothing happens, dialog could not be closed and no error
message appears

Expected Results:  Either close the dialog or (if national characters are
detected and not supported), show messagebox

Additional info:

Comment 1 Miloslav Trmac 2003-02-13 18:35:02 UTC
This seems to work fine in Phoebe: it asks the user not to use non-ASCII 
characters.

Comment 2 Brent Fox 2003-02-13 19:32:52 UTC
I agree.  I have made some changes in redhat-config-users in Phoebe that should
avoid this situation.


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