Bug 27861

Summary:	Installer (non-free option) fails with message "Failed to start Run Drakx installer X setup scripts."
Product:	Mageia	Reporter:	B K <baksocial>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	baksocial, mageia, marja11
Version:	8	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	journalctl messages

Description B K 2020-12-18 00:58:01 CET

Description of problem: The Mageia 8 Beta 2 Plasma ISO, when booted with the non-free option to boot either live environment or the installer fails because the drakx-installer-xsetup.service can't start.


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

Mageia 8 Beta 2


How reproducible:

Tried twice, once booting to the non-free live environment and once to the non-free installer. Happened both times. I can switch virtual terminals and see that the a session has started but a graphical environment is not opened to the live environment desktop or the installer. The initial failure that cascades is the systemd service drakx-installer-xsetup.service failing to start.

journalctl messages:

TIMESTAMP HOST: systemd[1]: drakx-installer-xsetup.service: Failed with result code 'exit-code'.
TIMESTAMP HOST: systemd[1]: Failed to start: Run DrakX installer X setup scripts.

X server log /var/log/Xorg.0.log accessed through differnet virtual terminal

[   54.440] (WW) Falling back to old probe method for v4l
[   54.494] intel: waited 2020 ms for i915.ko driver to load
[   54.498] (WW) Falling back to old probe method for v4l
[   54.498] (EE) No devices detected. 
[   54.498] (EE)
Fatal server error:
[   54.498] (EE) no screens found(EE)
[   54.498] (EE)
Please consult the Mageia support ...

 


Steps to Reproduce:
1. Boot ISO.
2. Select non-free option in GRUB
3. Installer boots and runs but graphical environment is not started due to drakx-installer-xsetup.service failing to start.

Comment 1 B K 2020-12-18 01:06:28 CET

Created attachment 12099 [details]
journalctl messages

journalctl messages image

B K 2020-12-18 01:06:38 CET

CC: (none) => baksocial

Comment 2 Martin Whitaker 2020-12-18 10:53:02 CET

After switching to a virtual terminal, capture the full system log with

  journalctl -b > journal.log

Then mount another disk partition, either an internal disk or another USB stick, and copy the file there, e.g. if your partition is /dev/sda1

  mount /dev/sda1 /mnt
  cp journal.log /mnt/journal.log
  umount /mnt

Reboot into a working system that can access that partition, compress the journal.log file, and attach it to this bug report.

CC: (none) => mageia
Keywords: (none) => NEEDINFO

Comment 3 Marja Van Waes 2021-01-08 12:46:00 CET

@ B K

The information requested in comment 2 wasn't given, so closing this report.

Please reopen it when you can provide that information, especially if you still have this issue with coming Mageia 8 rc

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