'Twas brillig, and Frank Griffin at 06/11/12 12:28 did gyre and gimble: > This actually started with the last systemd drop, but it's still > happening with today's systemd drop. > > The boot proceeds and then stalls on tty1 with: > > [^[[1;32m OK ^[[0m] Started LSB: ProFTPD FTP server. > [^[[1;32m OK ^[[0m] Started LSB: Starts the postfix daemons. > [^[[1;32m OK ^[[0m] Started LSB: Video Disk Recorder. > [^[[1;31mFAILED^[[0m] Failed to start Wait for Plymouth Boot Screen to > Quit. > See 'systemctl status plymouth-quit-wait.service' for details. > [^[[1;32m OK ^[[0m] Reached target Multi-User. > [^[[1;32m OK ^[[0m] Reached target Graphical Interface. > > The DM (GDM) does not start.
> However, if you ALT-F2 to tty2, getty > comes up, and if you do "service dm start", the DM starts, oddly enough, > on tty1. That's not odd. gdm is meant to always come up on tty1. > So, apparently, GDM can clear tty1 and start normally if it actually > gets control, but whatever systemd is doing to start the DM either isn't > getting done or is failing prematurely. Can you check what "systemctl status prefdm.service" says immediately after booting? Cheers Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
