On 03/03/15 09:52, Yves-Alexis Perez wrote:
> On mar., 2015-03-03 at 03:59 +0000, Mike Gabriel wrote:
>> IMHO, if gettys don't come up properly, the system is rather broken
>> and this is a no-go for jessie.
>
> Sure, but I had the impression that this wasn't the case for lightdm
> (and slim), according to Simon initial email. And I can confirm
> plymouth+lightdm seems to work just fine with init=systemd here.
I don't know whether lightdm, slim and/or wdm are affected (which is why
I haven't cloned the bug already). The situation to test is:
* have systemd as init
* install plymouth, gdm3 and your favourite non-GDM DM implementation
(kdm in the original bug report)
* select the non-GDM DM implementation as the active DM
* enable plymouth by putting "splash" on the kernel command-line
I reproduced this for kdm by starting from a fresh task-standard
installation in a VM and adding gdm3, kdm and plymouth. I haven't tested
the other DMs in the same configuration so far.
S
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54f585ea.9070...@debian.org
