Comment # 4 on bug 1088937 from Dr. Werner Fink

    The head of /usr/lib/systemd/system/display-manager.service


    [Unit]
    Description=X Display Manager
    Requires=var-run.mount
    Conflicts=getty@tty7.service plymouth-quit.service
    After=ypbind.service gpm.service time-sync.target winbind.service
acpid.service
    Wants=remote-fs.target dbus.socket systemd-user-sessions.service
systemd-logind.service
    After=remote-fs.target dbus.socket systemd-user-sessions.service
systemd-logind.service getty@tty7.service plymouth-quit.service

    ... why has this conflict with plymouth-quit.service been added?  This
prevents that plymouth-quit.service is exexuted at all (IMHO)

    IMHO the head should look like

    [Unit]
    Description=X Display Manager
    Requires=var-run.mount
    Conflicts=getty@tty7.service
    After=ypbind.service gpm.service time-sync.target winbind.service
acpid.service
    Wants=remote-fs.target dbus.socket systemd-user-sessions.service
systemd-logind.service
    After=remote-fs.target dbus.socket systemd-user-sessions.service
systemd-logind.service
    After=getty@tty7.service plymouth-quit.service plymouth-quit-wait.service

    and yes I'm aware that then a short moment the output on tty7 is seen by
the user but X server will not run into a battle with pylmouthd