Bug 399241

Summary: YaST2 crashes at the start of the installation when installing in Japanese
Product: [openSUSE] openSUSE 11.0 Reporter: Mike Fabian <mfabian>
Component: InstallationAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Blocker    
Priority: P5 - None CC: mvidner, shinkichi.yamazaki, tiwai
Version: RC 3   
Target Milestone: ---   
Hardware: x86-64   
OS: Linux   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast2-backtrace.png
gdb backtrace on y2base crash with japanese installation

Description Mike Fabian 2008-06-11 12:04:36 UTC
YaST2 crashes at the start of the installation when installing in
Japanese.

I used qemu:

qemu-kvm -std-vga -no-quit -m 512 \
        -cdrom /mounts/dist/install/openSUSE-11.0-RC4/openSUSE-11.0-RC4-DVD-x86_64.iso \
	-boot d \
	-hda $NAME.img \
	-monitor stdio \
	-net nic,model=rtl8139 \
        -net user,hostname=$NAME \
	-vnc :5 \
	$@

selected Japanese in linuxrc and then did choose *all* defaults.

YaST2 crashes before the timezone dialog is reached.
Comment 1 Mike Fabian 2008-06-11 12:31:33 UTC
Could this be related to bug #385172 ?
Comment 2 Mike Fabian 2008-06-11 12:37:39 UTC
Created attachment 221495 [details]
yast2-backtrace.png

screen shot of qemu showing the end of /var/log/YaST2/y2log.

There is a core file in /.
Comment 3 Takashi Iwai 2008-06-11 12:44:10 UTC
I can confirm that this happens on a real machine installation, too.

YaST crashes rightly after pushing "Next" button in the first dialog containing the language/keyboard list and the license agreement.

The gdb backtrace is almost as same as above.
Comment 4 Takashi Iwai 2008-06-11 12:45:11 UTC
Created attachment 221499 [details]
gdb backtrace on y2base crash with japanese installation
Comment 5 Takashi Iwai 2008-06-11 12:55:36 UTC
Correction: it crashes after selecting new install / update, i.e. just before timezeone.

And, I can confirm that this happens also on i386, too.
Comment 6 Martin Vidner 2008-06-11 13:02:16 UTC
Ugh :-(

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