'Twas brillig, and JA Magallón at 03/04/12 02:48 did gyre and gimble:
On 04/03/2012 02:43 AM, Colin Guthrie wrote:
No.
plymouth-quit-wait will simply hang until plymouth quits of it's own
accrord. If you actively quit plymouth first via plymouth-quit then
there is literally no point in
Hi...
With latest updates, I noticed that GDM again started in tty2, and tty1 is
still stuck on bootscreen/plymouth dots.
I get a message on tty1 about wait-for-playmouth-quit failed, see systemctl
status
And GDM starts on tty2.
Something weird is happpening:
cicely:~# systemctl --all
On 04/03/2012 02:07 AM, JA Magallón wrote:
Hi...
With latest updates, I noticed that GDM again started in tty2, and tty1 is
still stuck on bootscreen/plymouth dots.
I get a message on tty1 about wait-for-playmouth-quit failed, see systemctl
status
And GDM starts on tty2.
Something weird is
'Twas brillig, and JA Magallón at 03/04/12 01:13 did gyre and gimble:
On 04/03/2012 02:07 AM, JA Magallón wrote:
Hi...
With latest updates, I noticed that GDM again started in tty2, and
tty1 is
still stuck on bootscreen/plymouth dots.
I get a message on tty1 about wait-for-playmouth-quit
'Twas brillig, and Colin Guthrie at 03/04/12 01:43 did gyre and gimble:
'Twas brillig, and JA Magallón at 03/04/12 01:13 did gyre and gimble:
On 04/03/2012 02:07 AM, JA Magallón wrote:
Hi...
With latest updates, I noticed that GDM again started in tty2, and
tty1 is
still stuck on
