Bug 17710 - Initial welcome message (grub?) shows extra characters
Summary: Initial welcome message (grub?) shows extra characters
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-08 21:09 CET by David Remy
Modified: 2022-07-10 19:30 CEST (History)
5 users (show)

See Also:
Source RPM: grub
CVE:
Status comment:

Attachments
Pause VM Screenshot (15.84 KB, image/png)
2016-02-08 21:09 CET, David Remy 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description David Remy 2016-02-08 21:09:09 CET 
Created attachment 7427 [details]
Pause VM Screenshot

Testing Mageia-6-dev1-i586-DVD.iso with md5 1a2b7540062b5551d3766a479ef6ed92

The initial screen when booting, before gui starts, shows a Welcome message with explanation on how to repair and choose different boot options. This could be a grub menu, not too sure, but I attached a screenshot so someone can confirm.

I am running this is a VM, on Windows 10 1511 Hyper-V in Gen 1 (BIOS) mode.

The issue is that the message shows incorrect messages, such as "0aWelcome to 09Mageia0a install help07", "0ftext07", and "0e<Enter>07".
Comment 1 Marja Van Waes 2016-02-13 22:39:14 CET 
Assigning to all packagers collectively, since there is no maintainer for grub

Assignee: bugsquad => pkg-bugs
CC: (none) => marja11
Source RPM: (none) => grub

Comment 2 Thierry Vignaud 2016-06-17 11:55:45 CEST 
Anne, Thomas, didn't you fixed a similar bug for mga5?

Component: Installer => Release (media or process)
CC: (none) => ennael1, sysadmin-bugs, thierry.vignaud, tmb

Comment 3 sturmvogel 2022-07-10 19:30:51 CEST 
This was filed against MGA6 cauldron. MGA6 is EOL since Sep 2019. No response to comment 2 since 6 years...

Closing as OLD.

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