On 01/03/15 21:58, Simon McVittie wrote:
> On Sun, 09 Nov 2014 at 12:11:49 +0100, Laurent Bigonville wrote:
>> This bug is triggered by the fact that GDM systemd service is enabled
>> while KDM is also enabled. GDM .service file explicitly conflicts with
>> plymouth-quit.service as it calls "plymouth --quit" itself to allow a
>> smooth transition from plymouth to the login screen. To fix this part,
>> KDM should probably provides a .service file too and properly set a
>> symlink for display-manager.service (like GDM and lightdm are doing).
>
> One short path to a solution is to install this systemd "drop-in", which
> I have successfully tested in a jessie VM:
>
> smcv@debian:~$ cat /lib/systemd/system/kdm.service.d/after.conf
> [Unit]
> After=systemd-user-sessions.service getty@tty7.service plymouth-quit.service
> Conflicts=getty@tty7.service plymouth-quit.service
Looking at this again, I'm not at all sure that this is actually a
correct solution: the reason that gdm.service Conflicts with
plymouth-quit.service is that gdm wants to handle the Plymouth -> X11
transition itself, but kdm does not appear to do that. So I'm not sure
why this worked for me... (but it did).
> slim and lightdm do have native systemd .service files, but don't have
> those relationships, which I think is probably a bug in those DMs'
> service files
If they do not interact with plymouth themselves like gdm does, then it
is correct to not have this relationship.
lightdm does not appear to have this bug, so I will drop it from Cc in
future responses: when I installed both gdm3 and lightdm, everything
seemed to work fine.
slim does seem to have a superficially similar bug, although it is not
necessarily actually the same thing.
> The remaining provider of x-display-manager is wdm, which doesn't
> have a systemd service or any systemd drop-ins AFAICS, so it probably
> suffers from a bug analogous to #766462 with wdm taking kdm's place.
Yes, I have confirmed that it does. Steps to reproduce:
* install with GNOME in a virtual machine (you probably only need gdm3,
but I already had a GNOME VM left over from testing some other bug)
* apt-get install plymouth wdm
* choose to make wdm the default display manager
* edit /etc/default/grub and set GRUB_CMDLINE_LINUX_DEFAULT="quiet
splash"
* reboot
So if the best solution requires modifying kdm, this bug will likely
need to be cloned to wdm to make equivalent changes there.
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/54fec130.6000...@debian.org
