Bug 17237 - Plasma 5 LiveDVDs fail to boot into live mode
Summary: Plasma 5 LiveDVDs fail to boot into live mode
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-27 04:36 CET by Thomas Andrews
Modified: 2016-08-26 13:39 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
screenshots of Mageia 6 Plasma 5 6dev1 (702.14 KB, application/x-tar)
2015-11-27 04:43 CET, Thomas Andrews
Details

Description Thomas Andrews 2015-11-27 04:36:58 CET
Description of problem:
Neither of the LiveDVDs for Plasma 5 will boot into a live mode desktop. This happens with both real hardware and VirtualBox, on-board ATI or Intel graphics. It will show the Mageia splash screen, getting one or two "bubbles," after which it shows error messages about "no authority," and finally a blank screen.

I will be adding a tarball of several screenshots that may or may not aid in discovering the problem(s).



Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Andrews 2015-11-27 04:43:08 CET
Created attachment 7241 [details]
screenshots of Mageia 6 Plasma 5 6dev1

These shots were taken at various stages over several attempts to boot into Live mode. The 6.3 shot was taken as what most users would see just before the blank screen. The others were taken after pressing ESC on the keyboard.
Samuel Verschelde 2015-12-07 12:35:09 CET

Assignee: bugsquad => tmb

Samuel Verschelde 2015-12-07 12:35:28 CET

CC: (none) => mageia

Comment 2 Marja Van Waes 2016-08-26 13:39:35 CEST
@ Thomas Andrews,

Closing this one as OLD, because there was no activity since 9 months ago, which means that if the bug is still valid, there'll be a new 6sta1 or 6RC report for it.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.