Bug 145211 - SL10.1_LOC-Linux-JP-Beta1-06/01/24-Japanese YAST is very unstable
Summary: SL10.1_LOC-Linux-JP-Beta1-06/01/24-Japanese YAST is very unstable
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:45 UTC by Emmet Wildes
Modified: 2006-02-27 11:49 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:45:59 UTC 
Japanese YAST is very unstable.
For a number of different options in YAST when you repeat a task it will close out of the dialog and bring you back to YAST.

Similar issues already logged are 145135 & 145206

SL10.1
Japanese
Beta1

Steps:
1. Launch YAST.
2. Select System and then System Restoration.
3. Enable Local file and press the select button.
4. Cancel out of the restulting dialog and press the select button again.

Expected Result:
Dialog should pop-up for you to select a file.

Actual Result:
The second time you press the select button, the system restoration dialog closes down and returns to YAST.
Comment 1 Kerry OConnor 2006-01-26 12:06:35 UTC 
This is similar to issues 145135 and 145130. If the keyboard is set to input standard text it works fine, but if you hit SHIFT+SPACE to change to Japanese (when the dialog is open) and enter in Japanese characters it crashes out.
Comment 3 Stefan Hundhammer 2006-01-26 12:25:18 UTC 

*** This bug has been marked as a duplicate of 145130 ***
Comment 4 David Boyle 2006-01-26 15:57:00 UTC 
Sorry Stefan, we wanted to be sure that these are addressed. We will change our approach these and set them to normal going forward.
Comment 5 Barry McComish 2006-02-27 11:49:05 UTC 
Closing issue,see comment#3