Bug 805428

Summary: Anaconda crash after non-english language selection
Product: [Fedora] Fedora Reporter: Filip Skola <fskola>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: amarecek, anaconda-maint-list, g.kaviyarasu, jonathan, robatino, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-22 14:36:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda traceback none

Description Filip Skola 2012-03-21 09:38:41 UTC 
Description of problem:
After selection of another language anaconda crashes (or behaves strange).


Version-Release number of selected component (if applicable):
Fedora 17 Beta TC2


How reproducible:
always (tested in KVM)


Steps to Reproduce:
1. Select another language then English
2. Click Next
  

Additional info:
Tested crashes after selection of Czech, Spanish, Bulgarian, Ukrainian.

When English was selected, clicked next and than clicked back button, I was able to choose another language and rest of the installation seemed to go on well.

When I chose German, the crash occurred after clicking the back button in the keyboard selection window.


Clicking on Save button in anaconda crash window resulted in a blank screen.
Comment 1 Filip Skola 2012-03-21 09:44:12 UTC 
Tested with DVD and netinst ISOs.
Comment 2 Chris Lumens 2012-03-21 15:01:07 UTC 
Is your traceback the same as the one in bug 804817?
Comment 3 Filip Skola 2012-03-21 15:38:17 UTC 
Created attachment 571747 [details]
anaconda traceback
Comment 4 Chris Lumens 2012-03-22 14:36:30 UTC 
Marking as a dup even though it's not strictly the same traceback.  I believe there's some underlying issue regarding the anaconda environment leading to several similar tracebacks.

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