Bug 10236 - The DVD won't start. The message = cannot start, file or directory boot splash does not exits or is not available. How & where to find boot splash for mageia2?
Summary: The DVD won't start. The message = cannot start, file or directory boot spla...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-23 13:40 CEST by Joep van Ham
Modified: 2015-03-31 16:02 CEST (History)
1 user (show)

See Also:
Source RPM: Mageia-3-LiveDVD-KDE4-i586-DVD
CVE:
Status comment:

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

Description Joep van Ham 2013-05-23 13:40:28 CEST 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
I burned - with k3b - Mageia-3-LiveDVD-KDE4-i586-DVD as was available at Mageia download. The DVD won't start. The message = cannot start file or directory  boot splash. does not exits or is not available. How & where to find boot splash for mageia2 ?
TIA
Joep van Ham

Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-05-24 23:33:07 CEST 
when was prompted the message ?
Comment 2 Marja Van Waes 2015-03-31 16:02:55 CEST 
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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