Bug 875829 - unclear what Language spoke actually configures
Summary: unclear what Language spoke actually configures
Keywords:
Status: CLOSED DUPLICATE of bug 874263
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
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-11-12 16:02 UTC by Steve Tyler
Modified: 2012-11-12 17:03 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-12 17:03:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steve Tyler 2012-11-12 16:02:20 UTC
Description of problem:
The Welcome dialog and the Language spoke ask the same question at the top:

"What language would you like to use during the installation process?"

Asking the same question twice confuses the user about what the Language spoke configures that is different from what was configured in the Welcome dialog.

Version-Release number of selected component (if applicable):
anaconda 18.28
Fedora-18-Beta-TC8-x86_64-DVD.iso

How reproducible:
Always.

Steps to Reproduce:
1. Start installer.
2. Note question at top of Welcome dialog.
3. Click the Language spoke link.
4. Note question at top of Language spoke.
  
Actual results:
The same question is asked at the top of the Welcome dialog and the Language spoke:
"What language would you like to use during the installation process?"

Expected results:
The question at the top of the Language spoke asks a question that helps the user understand what the Language spoke configures.

Additional info:
Bug 874263 - Picking different languages at pre-hub selection screen and Language spoke causes installer to become a hybrid, and crash 

Tested with:
$ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Beta/TC8/Fedora-18-Beta-TC8-x86_64-DVD.iso -usb -vga qxl -boot menu=on -usbdevice mouse

Comment 1 Chris Lumens 2012-11-12 17:03:50 UTC
The fix for this is already outlined in bug 874263.  I don't need a second bug for it.

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


Note You need to log in before you can comment on or make changes to this bug.