Bug 145206 - SL10.1_LOC-Linux-JP-Beta1-06/01/24-Extended characters not getting accepted into profile name.
Summary: SL10.1_LOC-Linux-JP-Beta1-06/01/24-Extended characters not getting accepted i...
Status: VERIFIED DUPLICATE of bug 145130
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Emmet Wildes
URL:
Whiteboard:
Keywords: I18N, Japanese
Depends on:
Blocks:
 
Reported: 2006-01-24 15:32 UTC by Emmet Wildes
Modified: 2006-03-21 12:02 UTC (History)
1 user (show)

See Also:
Found By: Localization
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Emmet Wildes 2006-01-24 15:32:08 UTC 
Extended characters not getting accepted into profile name.

SL10.1
Japanese
Beta1

Steps:
1. Launch YAST.
2. Select System and then System Backup.
3. From Profile Management select Add.
4. Add a profile name with extended characters and press ok.

Expected Result:
Profile name to be added and not crash out.

Actual Result:
Profile name does not get added when you use extended characters and then closes out of System Backup dialog.

Note, it works fine when you use normal characters in profile name
Comment 1 Emmet Wildes 2006-01-24 15:32:33 UTC 
This also happens when you go to rename a profile name.

System backup dialog closes down.
Comment 2 Kerry OConnor 2006-01-26 11:52:54 UTC 
If the keyboard is set to input standard text it works fine, but if you hit SHIFT+SPACE to change to Japanese and enter in Japanese characters it crashes out.
Comment 3 Stefan Hundhammer 2006-01-26 12:39:35 UTC 
Say, if you come across a crash with one key combination in a dozen different scenarios, doesn't it ever occur to you that this is most likely ONE bug in some deeper system layer - like in X11 input methods or (less likely) in Qt?

*** This bug has been marked as a duplicate of 145130 ***