Description of problem:at the first boot after install in Virtual Box of the DE: LXDE (lxdm), MATE (LightDM), Xfce(LightDM), the boot-up fails with the above message - see attached image. Plasma5 (sddm) and Gnome(gdm) are ok Cinnamon starts in "software rendering mode" changing drakx11 settings does no seem to fix the problem changing drakdm to "xdm" does not seem to fix the problem. reboot the virtual box and the system boots up correctly to login greeter, and after login to desktop Version-Release number of selected component (if applicable): Mageia-6-RC-i586-DVD.iso DATE.txt: Fri Jul 15 20:00:00 CEST 2016 How reproducible:every time Steps to Reproduce: 1.install only LXDE, Mate Or Xfce DE from above .iso in a virtual box. reboot 2.boot up fails with text "there has been a problem starting your graphical display....good luck :)" 3.reboot the virtual box. login will be presented
Created attachment 8232 [details] "there has been a problem starting your graphical display"
Keywords: (none) => 6RCSummary: [6rc] Virtual Box, first boot after install fails with "there has been a problem starting your graphical display" => [6rc] first boot after install in Virtual Box fails with: "there has been a problem starting your graphical display"
Created attachment 8233 [details] report.bug.txt
Created attachment 8234 [details] lspcidrake -v
Haven't we seen something similar some years ago, that X wouldn't come up at the first boot, but came up fine after the next boots?
CC: (none) => davidwhodgins, eeeemail, manuel.mageia, marja11, thierry.vignaud, tmb
Btw, when that happens again, could you switch to e.g. tty3 (most likely with "right Ctrl"+"F3") and fetch a copy of: /var/log/Xorg.0.log and also do (as root) journalctl -ab > grep journal.txt and attach both the Xorg.0.log and journal.txt to this bug report?
Keywords: (none) => NEEDINFO
(In reply to Marja van Waes from comment #5) > Btw, when that happens again, could you switch to e.g. tty3 (most likely > with "right Ctrl"+"F3") and fetch a copy of: > > /var/log/Xorg.0.log > > and also do (as root) > > journalctl -ab > grep journal.txt > > and attach both the Xorg.0.log and journal.txt to this bug report? as "user": $ /var/log/Xorg.0.log -bash:/var/log/Xorg.0.log: no such file or directory as root: # /var/log/Xorg.0.log -bash: /var/log/Xorg.0.log: permission denied :( # journalctl -ab > grep journal.txt failed to add match "journal.txt": invalid argument :( drakdm and choosing "xdm" drakx11 and choosing "Xorg vesa" as graphics allows login
Created attachment 8260 [details] journal.txt maybe the journal.txt that failed to match above
hmmm. It seems that if the Oracle VM Virtual Box Extension Pack is not installed the problem occurs. Installing the Oracle VM Virtual Box Extension Pack causes the issue to no longer occur.
Sorry for the confusion with that command to get the journalctl output... my fingers tend to misbehave, "grep" shouldn't have been there. (In reply to ben mcmonagle from comment #8) > hmmm. > > It seems that if the Oracle VM Virtual Box Extension Pack is not installed > the problem occurs. > Installing the Oracle VM Virtual Box Extension Pack causes the issue to no > longer occur. Closing as worksforyou, then. Thanks for all the feedback :-)
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME