Bug 19032

Summary:	[6rc] first boot after install in Virtual Box fails with: "there has been a problem starting your graphical display"
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, eeeemail, manuel.mageia, marja11, thierry.vignaud, tmb
Version:	Cauldron	Keywords:	6sta1.5, NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	"there has been a problem starting your graphical display" report.bug.txt lspcidrake -v journal.txt

Description Ben McMonagle 2016-07-23 02:20:00 CEST

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

Comment 1 Ben McMonagle 2016-07-23 02:20:39 CEST

Created attachment 8232 [details]
"there has been a problem starting your graphical display"

Ben McMonagle 2016-07-23 02:22:08 CEST

Keywords: (none) => 6RC
Summary: [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"

Comment 2 Ben McMonagle 2016-07-23 02:25:27 CEST

Created attachment 8233 [details]
report.bug.txt

Comment 3 Ben McMonagle 2016-07-23 02:29:17 CEST

Created attachment 8234 [details]
lspcidrake -v

Comment 4 Marja Van Waes 2016-07-23 23:06:22 CEST

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

Comment 5 Marja Van Waes 2016-07-24 09:07:17 CEST

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

Comment 6 Ben McMonagle 2016-07-25 12:36:41 CEST

(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

Comment 7 Ben McMonagle 2016-07-25 12:39:31 CEST

Created attachment 8260 [details]
journal.txt

maybe the journal.txt that failed to match above

Comment 8 Ben McMonagle 2016-07-27 10:32:00 CEST

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.

Comment 9 Marja Van Waes 2016-07-27 23:17:07 CEST

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 => RESOLVED
Resolution: (none) => WORKSFORME