Bug 5487 - Impossible to configure X during the summary-step in stage2 of the installer
Summary: Impossible to configure X during the summary-step in stage2 of the installer
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-19 13:50 CEST by Kristoffer Grundström
Modified: 2012-04-19 17:00 CEST (History)
2 users (show)

See Also:
Source RPM: drakx-installer-stage2
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Kristoffer Grundström 2012-04-19 13:50:25 CEST 
Description of problem: I just tried to complete an installation of Cauldron using a VM & at the summary step I see this error when clicking the Next-button:

An error occurred
Type of argument to keys on reference must be unblessed hashref or arrayref.

Then I get asked if I'm sure I want to proceed without configuring X.

Version-Release number of selected component (if applicable): 14.5-2.mga2

How reproducible: Everytime I try to continue with the last step.

Steps to Reproduce:
1. Download boot.iso.
2. Burn it to a USB-stick/key.
3. Start the installation.
4. Get to the summary-part of the installer i stage2.
5. When you see that X isn't set, click the button to set it.
6. Now you'll see that message.
Kristoffer Grundström 2012-04-19 13:50:32 CEST

CC: (none) => kristoffer.grundstrom1983

Kristoffer Grundström 2012-04-19 13:51:03 CEST

Summary: Impossible to configure X during the boot-manager step => Impossible to configure X during the summary-step in stage2 of the installer

Kristoffer Grundström 2012-04-19 13:51:44 CEST

Priority: Normal => High

Thierry Vignaud 2012-04-19 16:43:31 CEST

CC: (none) => thierry.vignaud
Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2012-04-19 17:00:51 CEST 
Fixed in git

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.