| Summary: | media.cfg not found | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | gvs sastry <gvssastry.met> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | nic, thierry.vignaud |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
gvs sastry
2014-03-22 13:40:22 CET
Hi, sorry your bug report was overlooked. It could have been a faulty DVD. Can you test if you can reproduce with Mageia 5RC? If you can, when the error occurs, do not reboot directly, but rather open a console with Ctrl + Alt + F2, insert an usb stick, and type "bug". This should copy a file named report.bug to it, that you will be able to attach to this bug report so that we can see what happened. If you can't, we'll probably close this bug report as old since we can't fix Mageia 4 installers. Keywords:
(none) =>
NEEDINFO Reducing severity as this has only be seen by one person. CC:
(none) =>
thierry.vignaud Installer and Release bugs should always be set to cauldron, because once the isos for a stable version have been created, they cannot be changed. This bug was filed very long ago, for Mageia 4. Was this bug still valid for Mageia 5? (If so, please do _not_ set the version to "5". Only asking because if it was still valid for Mageia 5, that then we'll know we'll have to pay attention to this issue when testing the 6 alpha's and later). Please close this bug report if the problem was solved in Mageia 5hhhh Version:
4 =>
Cauldron Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |