Description of problem: gdm does not start automatically after install. Needs to always switch with ctrl+f2 to tty console and launch "systemctl start gdm.service" manually as a root user. Version-Release number of selected component (if applicable): Latest Mageia cauldron installed on 29.5.2018. Kernel version is: 4.14.44-desktop-2.mga7 How reproducible: Always (on every boot) Steps to Reproduce: 1) flashed and booted Mageia-Cauldron-all-nonfree-x86_64.img 2) selected the gnome from install menu and installed the Mageia 7 (cauldron) succesfully over internet http mirrors 3) booted to Mageia --> Boot stops to black screen/no gdm login page is displayed 4) switch to another tty with ctrl+f2 and login to system via tty console 5) systemctl status gdm.service shows that the service is died 6) systemctl start gdm.service --> GDM login UI opens and I can login to gnome
Hi Mika, thanks for the report. Please attach 1. /root/drakx/report.bug.xz and also 2. log.txt that is the result of running, as root, journalctl -ab > log.txt right after reproducing the problem (so right after switching to tty2 when you don't get the GDM screen). Thanks :-)
Source RPM: (none) => drakx-installer-stage2?, systemd? gdm?CC: (none) => basesystem, gnome, mageiatools, marja11Keywords: (none) => NEEDINFO
Created attachment 10216 [details] report.bug.xz after gdm did not start automatically after boot.
Created attachment 10217 [details] journalctl log file after gdm did not start automatically after boot.
# systemctl status gdm.service ● gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled) Active: inactive (dead)
see workarounds in bug 22620 and bug 22593
CC: (none) => bittwister2
(In reply to Mika Laitio from comment #3) > Created attachment 10217 [details] > journalctl log file after gdm did not start automatically after boot. Indeed, it doesn't even attmmpt to start. (In reply to Bit Twister from comment #5) > see workarounds in bug 22620 and bug 22593 Bit Twister is right, it looks like the same issue as those bugs. running as root: systemctl set-default graphical.target should fix the issue. Please try :-)
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=22620, https://bugs.mageia.org/show_bug.cgi?id=22593Source RPM: drakx-installer-stage2?, systemd? gdm? => drakx-installer-stage2
(In reply to Marja Van Waes from comment #6) > > running as root: > > systemctl set-default graphical.target > > should fix the issue. Please try :-) And report here whether that works!
Yes, the execution of systemctl set-default graphical.target as a root fixes the issue.
(In reply to Mika Laitio from comment #8) > Yes, the execution of > > systemctl set-default graphical.target > > as a root fixes the issue. Thanks :-) So this is a duplicate of bug 22593 *** This bug has been marked as a duplicate of bug 22593 ***
Resolution: (none) => DUPLICATEStatus: NEW => RESOLVED