Bug 68

Summary:	first bootup after installation has F1, F2, F3, but no visible text.
Product:	Mageia	Reporter:	AL13N <alien>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	release_blocker	CC:	dglent, dmorganec, shikamaru
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description AL13N 2011-02-16 23:51:39 CET

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101230 Mandriva Linux/1.9.2.13-0.2mdv2010.2 (2010.2) Firefox/3.6.13
Build Identifier: 

Description of problem:

in the grub/gfxboot screen after installation and during first boot, F1 F2 F3 have no text...

Reproducible: 

Steps to Reproduce:

Rémy CLOUARD (shikamaru) 2011-02-21 22:34:58 CET

Priority: Normal => release_blocker
CC: (none) => shikamaru

D Morgan 2011-02-25 00:03:42 CET

CC: (none) => dmorganec
Assignee: ahmadsamir3891 => bugsquad

Comment 1 Remco Rijnders 2011-02-26 11:14:55 CET

*** Bug 178 has been marked as a duplicate of this bug. ***

CC: (none) => dglent

Comment 2 AL13N 2011-03-18 18:26:15 CET

fixed in mageia 1 alpha 2

AL13N 2011-03-18 18:26:50 CET

Blocks: (none) => 56

Comment 3 Ahmad Samir 2011-03-18 23:33:00 CET

@AL13N, not an upgrade-related bug (how many other reports did you set as blocking 56?).

Status: NEW => RESOLVED
Blocks: 56 => (none)
Resolution: (none) => FIXED

Comment 4 AL13N 2011-03-19 02:17:45 CET

all the ones that were working in mandriva 2010.1 and not anymore after upgrading to mageia 1 alpha 2.

i think you are mistaken in removing all those dependencies, wasn't the tracker specifically made to make sure the upgrade path is valid? and completely successfull?

i don't think this tracker is just used for direct upgrade errors during installation itself. all broken packages after installation are IMHO also blocking the upgrade.

Comment 5 Ahmad Samir 2011-03-19 05:29:56 CET

(In reply to comment #4)
> all the ones that were working in mandriva 2010.1 and not anymore after
> upgrading to mageia 1 alpha 2.
> 
> i think you are mistaken in removing all those dependencies, wasn't the tracker
> specifically made to make sure the upgrade path is valid? and completely
> successfull?
> 
> i don't think this tracker is just used for direct upgrade errors during
> installation itself. all broken packages after installation are IMHO also
> blocking the upgrade.

The scope of bug 56 is "bugs that happen during the upgrade process", e.g.:
- if an mdv package doesn't get replaced by its mga counterpart (e.g. task-x11-2010.1 in mdv and task-x11-1- in mga)
- if there're file conflicts due to files moving from one package to another
- if the post/postun scriptlets don't get executed due to name change (e.g. mandriva-gfxboot-theme >> mageia-gfxboot-theme)

Let's take this bug report for example, it's about a bug in mageia-gfxboot-theme, it's not an upgrade issue simply because you'd get the same exact bug with a clean install of Alpha1.

Another issue is, what's the point of marking bug reports that have already been _fixed_ as blocking of a tracker bug? the whole point of having a tracker is to easily examine all the reports that block it to fix them, if they're already fixed, what's the point?