Bug 805428 - Anaconda crash after non-english language selection
Summary: Anaconda crash after non-english language selection
Keywords:
Status: CLOSED DUPLICATE of bug 804817
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-21 09:38 UTC by Filip Skola
Modified: 2016-05-05 04:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-22 14:36:30 UTC
Type: ---

Attachments (Terms of Use)
anaconda traceback (122.72 KB, text/plain)
2012-03-21 15:38 UTC, Filip Skola 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.