<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] plymouth gone nuts ?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20plymouth%20gone%20nuts%20%3F&In-Reply-To=%3C4F7A56EF.5010505%40ono.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="013834.html">
<LINK REL="Next" HREF="013844.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] plymouth gone nuts ?</H1>
<B>JA Magallón</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20plymouth%20gone%20nuts%20%3F&In-Reply-To=%3C4F7A56EF.5010505%40ono.com%3E"
TITLE="[Mageia-dev] plymouth gone nuts ?">jamagallon at ono.com
</A><BR>
<I>Tue Apr 3 03:48:31 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="013834.html">[Mageia-dev] plymouth gone nuts ?
</A></li>
<LI>Next message: <A HREF="013844.html">[Mageia-dev] plymouth gone nuts ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13837">[ date ]</a>
<a href="thread.html#13837">[ thread ]</a>
<a href="subject.html#13837">[ subject ]</a>
<a href="author.html#13837">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 04/03/2012 02:43 AM, Colin Guthrie wrote:
><i> 'Twas brillig, and JA Magallón at 03/04/12 01:13 did gyre and gimble:
</I>>><i> On 04/03/2012 02:07 AM, JA Magallón wrote:
</I>>>><i> Hi...
</I>>>><i>
</I>>>><i> With latest updates, I noticed that GDM again started in tty2, and
</I>>>><i> tty1 is
</I>>>><i> still stuck on bootscreen/plymouth dots.
</I>>>><i> I get a message on tty1 about "wait-for-playmouth-quit failed, see
</I>>>><i> systemctl status...".
</I>>>><i> And GDM starts on tty2.
</I>>>><i> Something weird is happpening:
</I>>>><i>
</I>>>><i> cicely:~# systemctl --all --full | grep plym
</I>>>><i> systemd-ask-password-plymouth.path loaded active waiting Forward
</I>>>><i> Password Requests to Plymouth Directory Watch
</I>>>><i> plymouth-quit-wait.service loaded failed failed Wait for Plymouth Boot
</I>>>><i> Screen to Quit
</I>>>><i> plymouth-quit.service loaded inactive dead Terminate Plymouth Boot Screen
</I>>>><i> plymouth-read-write.service loaded inactive dead Tell Plymouth To
</I>>>><i> Write Out Runtime Data
</I>>>><i> plymouth-start.service loaded inactive dead Show Plymouth Boot Screen
</I>>>><i> systemd-ask-password-plymouth.service loaded inactive dead Forward
</I>>>><i> Password Requests to Plymouth
</I>>>><i>
</I>>>><i> cicely:~# ps -ef | grep plym
</I>>>><i> root 161 1 0 01:56 ? 00:00:00 /bin/plymouthd --attach-to-session
</I>>>><i> --pid-file /run/plymouth/pid
</I>>>><i> root 29109 8671 0 02:05 pts/1 00:00:00 grep --color plym
</I>>>><i>
</I>>>><i> Any idea ?
</I>>>><i>
</I>>><i>
</I>>><i> I have noticed this, plz correct me if I'm wrong:
</I>>><i>
</I>>><i> werewolf:/lib/systemd/system# grep After display-manager.service
</I>>><i> After=livesys-late.service systemd-user-sessions.service
</I>>><i> After=<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">getty at tty1.service</A> plymouth-quit.service
</I>>><i>
</I>>><i> werewolf:/lib/systemd/system# grep After plymouth-quit.service
</I>>><i> After=rc-local.service plymouth-start.service
</I>>><i>
</I>>><i> werewolf:/lib/systemd/system# grep After plymouth-quit-wait.service
</I>>><i> After=rc-local.service plymouth-start.service
</I>>><i>
</I>>><i> Should not all the chain be:
</I>>><i>
</I>>><i> display-manager.service -> after plymouth-quit-wait.service
</I>>><i> plymouth-quit-wait.service -> after plymouth-quit.service
</I>><i>
</I>><i> No.
</I>><i>
</I>><i> plymouth-quit-wait will simply hang until plymouth quits of it's own
</I>><i> accrord. If you actively quit plymouth first via plymouth-quit then
</I>><i> there is literally no point in running plymouth-quit-wait as it'll just
</I>><i> exit immediately.
</I>><i>
</I>
Ah, thanks. I jus thought that 'plymouth quit' was asynchronous,
and the -wait script just made sure to wait before launching DM...
><i> Also u're forgetting about the Conflicts= directives...
</I>><i>
</I>><i> display-manager.service:Conflicts=<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">getty at tty1.service</A> plymouth-quit.service
</I>><i>
</I>><i> display-manager specifically conflicts with plymouth-quit.service (as it
</I>><i> internally quits plymouth or allows a smooth transition if appropriate).
</I>><i>
</I>><i> So the ordering is correct as it stands.
</I>><i>
</I>><i> Now the question is what is preventing plymouth from being quit? As I
</I>><i> said, display-manager should do it for you (see the /etc/X11/prefdm
</I>><i> script), or simply let GDM do it itself.
</I>><i>
</I>><i> I'll see what I can dig up.
</I>><i>
</I>><i> Col
</I>><i>
</I>><i>
</I>><i>
</I>
--
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="013834.html">[Mageia-dev] plymouth gone nuts ?
</A></li>
<LI>Next message: <A HREF="013844.html">[Mageia-dev] plymouth gone nuts ?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#13837">[ date ]</a>
<a href="thread.html#13837">[ thread ]</a>
<a href="subject.html#13837">[ subject ]</a>
<a href="author.html#13837">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>