Debian Bug report logs - #766462
with plymouth installed, and both GDM and KDM enabled, I don't get any gettys on my VCs

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Peter Palfrader <weasel@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: with plymouth installed, I don't get any gettys on my VCs

Date: Thu, 23 Oct 2014 12:13:44 +0200

Package: plymouth
Version: 0.9.0-7
Severity: serious

Hi,

I just upgraded to jessie, and with plymouth installed, I don't get
any gettys/login prompts on any of the VCs.  kdm starts up and gives me
an X login-prompt, but none of the consoles do.

Purging plymoth gives me login prompts on the VCs.

Cheers,

Message #10 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Laurent Bigonville <bigon@debian.org>

To: Peter Palfrader <weasel@debian.org>

Cc: 766462@bugs.debian.org

Subject: Re: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 28 Oct 2014 11:32:22 +0100

tag 766462 + moreinfo unreproducible
thanks

Hello Peter,

Could you please add a bit more information here? Which architectures
are you talking about? is your system completely up-to-date? Which init
system are you using?

I definitely cannot reproduce this on my amd64 machine running an
up-to-date sid and systemd.

Could you also please try to add plymouth.debug to the kernel cmdline,
it should create a plymouth-debug.log in /var/log. Please attach the
file here.

Cheers,

Laurent Bigonville

Message #17 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Peter Palfrader <weasel@debian.org>

To: Laurent Bigonville <bigon@debian.org>

Cc: 766462@bugs.debian.org

Subject: Re: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 28 Oct 2014 11:36:38 +0100

On Tue, 28 Oct 2014, Laurent Bigonville wrote:

> tag 766462 + moreinfo unreproducible
> thanks
> 
> Hello Peter,
> 
> Could you please add a bit more information here? Which architectures
> are you talking about? is your system completely up-to-date? Which init
> system are you using?

amd64, current jessie, systemd.

> I definitely cannot reproduce this on my amd64 machine running an
> up-to-date sid and systemd.
> 
> Could you also please try to add plymouth.debug to the kernel cmdline,
> it should create a plymouth-debug.log in /var/log. Please attach the
> file here.

I'll see what I can do tonight.

Cheers,
-- 
                           |  .''`.       ** Debian **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/

Message #22 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Peter Palfrader <weasel@debian.org>

To: Laurent Bigonville <bigon@debian.org>

Cc: 766462@bugs.debian.org

Subject: Re: with plymouth installed, I don't get any gettys on my VCs

Date: Thu, 6 Nov 2014 21:43:57 +0100

On Tue, 28 Oct 2014, Laurent Bigonville wrote:

> Could you please add a bit more information here? Which architectures
> are you talking about? is your system completely up-to-date? Which init
> system are you using?

amd64, completely up to date jessie, /sbin/init is provided by systemd-sysv.

> Could you also please try to add plymouth.debug to the kernel cmdline,
> it should create a plymouth-debug.log in /var/log. Please attach the
> file here.

Did that, didn't get a logfile.

Let me know how I can help.
-- 
                           |  .''`.       ** Debian **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/

Message #27 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Peter Palfrader <weasel@debian.org>

To: Laurent Bigonville <bigon@debian.org>

Cc: 766462@bugs.debian.org

Subject: Re: with plymouth installed, I don't get any gettys on my VCs

Date: Thu, 6 Nov 2014 21:48:15 +0100

On Thu, 06 Nov 2014, Peter Palfrader wrote:

> Did that, didn't get a logfile.

} weasel@defiant:/var/log$ cat /proc/cmdline 
} BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/vg0-root ro splash quiet plymouth.debug
} weasel@defiant:/var/log$ ls -l pl*        
} zsh: no matches found: pl*

However, removing "splash" from the kernel command line (it was set in
/etc/default/grub from my wheezy), makes gettys work on the VCs again.

Cheers,
-- 
                           |  .''`.       ** Debian **
      Peter Palfrader      | : :' :      The  universal
 http://www.palfrader.org/ | `. `'      Operating System
                           |   `-    http://www.debian.org/

Message #32 received at 766462@bugs.debian.org (full text, mbox, reply):

From: intrigeri <intrigeri@debian.org>

To: Peter Palfrader <weasel@debian.org>

Cc: 766462@bugs.debian.org

Subject: Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Sat, 08 Nov 2014 16:58:05 +0100

Hi,

Peter Palfrader wrote (06 Nov 2014 20:48:15 GMT) :
> On Thu, 06 Nov 2014, Peter Palfrader wrote:

>> Did that, didn't get a logfile.

> } weasel@defiant:/var/log$ cat /proc/cmdline 
> } BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/vg0-root ro splash quiet plymouth.debug
> } weasel@defiant:/var/log$ ls -l pl*        
> } zsh: no matches found: pl*

Strange. I do get /var/log/plymouth-debug.log when booting with
plymouth.debug (current sid, amd64, plymouth 0.9.0-8).

Maybe the content of /etc/plymouth/plymouthd.conf, and the output of
these commands, would tell us more:

  for service in log quit quit-wait read-write start ; do
     systemctl status "plymouth-$service.service"
  done

(after booting with "splash plymouth.debug")

Cheers,
--
intrigeri

Message #37 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Laurent Bigonville <bigon@debian.org>

To: 766462@bugs.debian.org

Cc: Peter Palfrader <weasel@debian.org>

Subject: Re: with plymouth installed, I don't get any gettys on my VCs

Date: Sun, 9 Nov 2014 12:11:49 +0100

On Thu, 23 Oct 2014 12:13:44 +0200 Peter Palfrader <weasel@debian.org>
wrote:
> Package: plymouth
> Version: 0.9.0-7
> Severity: serious
> 
> Hi,
> 
> I just upgraded to jessie, and with plymouth installed, I don't get
> any gettys/login prompts on any of the VCs.  kdm starts up and gives
> me an X login-prompt, but none of the consoles do.
> 
> Purging plymoth gives me login prompts on the VCs.

So small summary of what's happening here. After some debugging with
weasel it turns out that:

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).

Looking at other .service file (like console-getty.service or
getty@.service) it turns out that they declare an
"After=plymouth-quit-wait.service" relationship. That might explain why
the getty's are not started.

Not too sure how to fix this at this point in the development process,
maybe plymouth-quit-wait.service should have some kind of timeout?
(ATM it's explicitly disabling the timeout). But this should be tested,
the side effect is that plymouthd would never exit not 100% sure if
this has other implications.

As a side note, the fact that the debug log is not generated is because
the file is written to disk only when the daemon exits...

Cheers,

Laurent Bigonville

Message #48 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: 766462@bugs.debian.org

Subject: reassign to KDM?

Date: Tue, 16 Dec 2014 17:49:56 +0000

[Message part 1 (text/plain, inline)]

Hi Laurent,

I just stumbled over the same issue (no tty logins with KDM as display  
manager while gdm3 is installed).

From what you wrote [1], this bug should be reassigned to KDM? I also  
consider it a serious issue.

Mike

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766462#37

-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

Message #55 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Laurent Bigonville <bigon@debian.org>, 766462@bugs.debian.org, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Cc: Peter Palfrader <weasel@debian.org>, kdm@packages.debian.org, lightdm@packages.debian.org, slim@packages.debian.org, wdm@packages.debian.org

Subject: Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Sun, 1 Mar 2015 21:58:27 +0000

Cc kdm, lightdm, slim, wdm maintainers to warn you that you might be
getting a RC bug (with a simple fix, add one 3-line file) assigned or
cloned to your DM implementations.

Peter Palfrader wrote:
> I just upgraded to jessie, and with plymouth installed, I don't get
> any gettys/login prompts on any of the VCs.  kdm starts up and gives me
> an X login-prompt, but none of the consoles do.

(The bad situation is: plymouth, gdm3 and kdm are all installed; kdm
is selected as the x-display-manager implementation; and plymouth
is enabled via "splash" on the kernel command-line.)

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

(In particular, because systemd generates equivalent native systemd units
for sysvinit scripts, you don't actually have to write a native systemd
unit for that drop-in to work.)

I copied those from gdm3, but lxdm has the same. plymouth-quit.service is
for this bug, getty@tty7.service is to avoid that getty fighting with
*dm for control over the tty, and systemd-user-sessions.service is meant
to run before any user can log in.

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; they should probably gain those lines too. However,
because they participate in managing the display-manager.service
symlink, they suppress gdm.service altogether, so they might avoid
get this problem with the plymouth handover.

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.

Adding the reverse relationships (Conflicts and Before) to
plymouth-quit.service for all known DMs in jessie is tempting,
since that would only require patching one package, but it probably
isn't a great idea since Conflicts is not entirely symmetric:
if systemd runs a transaction that is trying to start A and B,
something Requires A, something Requires B, and A has Conflicts=B,
then it is A that will "win" and be started. So my recommendation
would be to change the display managers.

    S

Message #60 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Yves-Alexis Perez <corsac@debian.org>

To: Simon McVittie <smcv@debian.org>

Cc: Laurent Bigonville <bigon@debian.org>, 766462@bugs.debian.org, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, kdm@packages.debian.org, lightdm@packages.debian.org, Peter Palfrader <weasel@debian.org>, wdm@packages.debian.org, slim@packages.debian.org

Subject: Re: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Mon, 02 Mar 2015 21:30:49 +0100

[Message part 1 (text/plain, inline)]

On dim., 2015-03-01 at 21:58 +0000, Simon McVittie wrote:
> 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; they should probably gain those lines too. However,
> because they participate in managing the display-manager.service
> symlink, they suppress gdm.service altogether, so they might avoid
> get this problem with the plymouth handover.

So what's your advice here for lightdm? Maybe it's worth adding it, but
it doesn't warrant a freeze exception?

Regards,
-- 
Yves-Alexis

[signature.asc (application/pgp-signature, inline)]

Message #65 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: Yves-Alexis Perez <corsac@debian.org>

Cc: Simon McVittie <smcv@debian.org>, Laurent Bigonville <bigon@debian.org>, 766462@bugs.debian.org, kdm@packages.debian.org, lightdm@packages.debian.org, Peter Palfrader <weasel@debian.org>, wdm@packages.debian.org, slim@packages.debian.org

Subject: Re: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 03 Mar 2015 03:59:53 +0000

[Message part 1 (text/plain, inline)]

Hi all, hi Yves-Alexis,

On  Mo 02 Mär 2015 21:30:49 CET, Yves-Alexis Perez wrote:

> On dim., 2015-03-01 at 21:58 +0000, Simon McVittie wrote:
>> 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; they should probably gain those lines too. However,
>> because they participate in managing the display-manager.service
>> symlink, they suppress gdm.service altogether, so they might avoid
>> get this problem with the plymouth handover.
>
> So what's your advice here for lightdm? Maybe it's worth adding it, but
> it doesn't warrant a freeze exception?
>
> Regards,

I am quite positive that some missing gettys because of two DMs being  
installed in parallel (or some similar normal thing that people might  
do) will definitely be worth a freeze exception.

IMHO, if gettys don't come up properly, the system is rather broken  
and this is a no-go for jessie.

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

Message #70 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Yves-Alexis Perez <corsac@debian.org>

To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Cc: lightdm@packages.debian.org, Peter Palfrader <weasel@debian.org>, wdm@packages.debian.org, slim@packages.debian.org, Laurent Bigonville <bigon@debian.org>, Simon McVittie <smcv@debian.org>, kdm@packages.debian.org, 766462@bugs.debian.org

Subject: Re: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 03 Mar 2015 10:52:19 +0100

[Message part 1 (text/plain, inline)]

On mar., 2015-03-03 at 03:59 +0000, Mike Gabriel wrote:
> I am quite positive that some missing gettys because of two DMs being  
> installed in parallel (or some similar normal thing that people might  
> do) will definitely be worth a freeze exception.
> 
> 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.

Regards,
-- 
Yves-Alexis

[signature.asc (application/pgp-signature, inline)]

Message #75 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Yves-Alexis Perez <corsac@debian.org>, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Cc: lightdm@packages.debian.org, Peter Palfrader <weasel@debian.org>, wdm@packages.debian.org, slim@packages.debian.org, Laurent Bigonville <bigon@debian.org>, kdm@packages.debian.org, 766462@bugs.debian.org

Subject: Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 03 Mar 2015 09:59:06 +0000

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

Message #80 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Yves-Alexis Perez <corsac@debian.org>

To: Simon McVittie <smcv@debian.org>

Cc: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, lightdm@packages.debian.org, Peter Palfrader <weasel@debian.org>, wdm@packages.debian.org, slim@packages.debian.org, Laurent Bigonville <bigon@debian.org>, kdm@packages.debian.org, 766462@bugs.debian.org

Subject: Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 03 Mar 2015 11:04:36 +0100

[Message part 1 (text/plain, inline)]

On mar., 2015-03-03 at 09:59 +0000, Simon McVittie wrote:
> * have systemd as init
> * install plymouth, gdm3 and your favourite non-GDM DM implementation
>   (kdm in the original bug report)

Ok, I'm missing gdm3 here, so I'll try to install it and report back on
the situation.

> * select the non-GDM DM implementation as the active DM
> * enable plymouth by putting "splash" on the kernel command-line

Regards,
-- 
Yves-Alexis

[signature.asc (application/pgp-signature, inline)]

Message #85 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Laurent Bigonville <bigon@debian.org>, 766462@bugs.debian.org, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Cc: Peter Palfrader <weasel@debian.org>, kdm@packages.debian.org, lightdm@packages.debian.org, slim@packages.debian.org, wdm@packages.debian.org

Subject: Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 10 Mar 2015 10:02:24 +0000

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

Message #90 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Yves-Alexis Perez <corsac@debian.org>

To: Simon McVittie <smcv@debian.org>

Cc: Laurent Bigonville <bigon@debian.org>, 766462@bugs.debian.org, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, kdm@packages.debian.org, lightdm@packages.debian.org, Peter Palfrader <weasel@debian.org>, wdm@packages.debian.org, slim@packages.debian.org

Subject: Re: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Tue, 10 Mar 2015 13:32:01 +0100

[Message part 1 (text/plain, inline)]

On mar., 2015-03-10 at 10:02 +0000, Simon McVittie wrote:
> > 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.

Actually lightdm tries to interact with plymouth
(http://sources.debian.net/src/lightdm/1.10.3-3/src/plymouth.c/)
> 
> 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.

Ok, fine for me :)

Regards,
-- 
Yves-Alexis

[signature.asc (application/pgp-signature, inline)]

Message #95 received at 766462@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Laurent Bigonville <bigon@debian.org>, 766462@bugs.debian.org, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Cc: Peter Palfrader <weasel@debian.org>, kdm@packages.debian.org, gdm3@packages.debian.org, slim@packages.debian.org, wdm@packages.debian.org

Subject: Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Date: Wed, 11 Mar 2015 12:28:12 +0000

[Message part 1 (text/plain, inline)]

Control: reassign 766462 gdm3
Control: affects 766462 kdm wdm plymouth
Control: tags 766462 = patch pending

On 01/03/15 21:58, Simon McVittie wrote:
> Cc kdm, lightdm, slim, wdm maintainers to warn you that you might be
> getting a RC bug (with a simple fix, add one 3-line file) assigned or
> cloned to your DM implementations.

The real bug is that kdm and wdm do not participate in the shared
display-manager.service symlink management (#755359, #761642) which
should be fixed post-jessie. However, at the same time, it is gdm3 that
is doing something unusual (by suppressing plymouth-quit.service), so it
should probably also be gdm3 that mitigates bad situations caused by
that unusual configuration; and the same configuration in gdm3 can make
other broken situations worse (#780257, which I opened after thinking
about this some more). So I think gdm3 is probably the best place to fix
this particular symptom, particularly since the fix is easy.

I plan to upload the attached changes when my previous gdm3 upload has
migrated.

Regards,
    S

[gdm3_3.14.1-6.patch (text/x-patch, attachment)]

Message #108 received at 766462-close@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: 766462-close@bugs.debian.org

Subject: Bug#766462: fixed in gdm3 3.14.1-6

Date: Wed, 11 Mar 2015 21:18:51 +0000

Source: gdm3
Source-Version: 3.14.1-6

We believe that the bug you reported is fixed in the latest version of
gdm3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 766462@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <smcv@debian.org> (supplier of updated gdm3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 11 Mar 2015 12:25:38 +0000
Source: gdm3
Binary: gdm3 libgdm1 libgdm-dev gir1.2-gdm3
Architecture: source
Version: 3.14.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Description:
 gdm3       - GNOME Display Manager
 gir1.2-gdm3 - GObject introspection data for the GNOME Display Manager
 libgdm-dev - GNOME Display Manager (development files)
 libgdm1    - GNOME Display Manager (shared library)
Closes: 766462 780257
Changes:
 gdm3 (3.14.1-6) unstable; urgency=medium
 .
   * Team upload.
   * Under systemd, if gdm fails to start, or if the selected DM is
     kdm or wdm, make sure to run plymouth-quit.service (which gdm normally
     suppresses), so that plymouth-quit-wait.service terminates and gettys
     are not prevented from running. (Closes: #766462, #780257)
Checksums-Sha1:
 5323567cc22ce749aa7f29db4501d9a35c35b5e1 3143 gdm3_3.14.1-6.dsc
 ecc5cde6c72d47e8dfbf9648c268d7a19b723b4c 87284 gdm3_3.14.1-6.debian.tar.xz
Checksums-Sha256:
 0a21aa261a79ed1f36cfc286088e29ef55a73784b04d70bf97286c906d7a38fa 3143 gdm3_3.14.1-6.dsc
 f08136c5e226bc3d1e4c59cde539336c4d16b01a1eb7644d2921eba75d9059ed 87284 gdm3_3.14.1-6.debian.tar.xz
Files:
 a0ee8b1684494e00afc2130b0b35d1b9 3143 gnome optional gdm3_3.14.1-6.dsc
 82be214611fe3befe30f48a6232bbec6 87284 gnome optional gdm3_3.14.1-6.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIVAwUBVQCnfk3o/ypjx8yQAQjsiQ//WiihqtwH06+GP6A0uCxiNchKrUKnIeXV
I1X081TYKcag64Qn1il0btn+fSOsOIBnM2xdLkypAK0yGdnNyn2qYLDONvb7ynk5
IIRO8iLOKY7fZt7ltozVHGXVj775MdB3svg4tbIC8heKIb+I1yY/1zXF0MbCQO5W
dcjk0cpMuSm+I1MIq1Wder00FqDaCDyOjL/ZCz5ivrUAbbwymlFkBRLTgvgKA6iT
UQo+gTjQn3iCm8w25C8ekouuWo0BkE6ON1x9o/GBu/vLhzVW8aJHAaGp4jLPPhE9
Wq/BT5ITsdR2CPYADwMCpvmTGkVSjPu9Ec20W5Fk3hUR5+wLK50nWYQno0FWAdsh
jRFk3HoHR4lJU4LSXHAU1D2/NcV6yK8a1sVpnu1R64T+/7x6WcMzrkciz2sJNRUd
UmQ4tG8LKAI7vtFx0tRJzGXFb/FG+YthgtqkvlSp6IoDUCDuMk9kXfDQfj72HJE/
tM5Ir/dPCZvIMkpzLbK6pSSI+tqpss3CHD+do8fFAqwKfBCk8q3EFmtmO8poH1UR
m/F8cLKYBmBlXReJNVs3ZZTxjNzY/xqtcfhrQOISD8foRC5CdIsVOiVRuRvuGfPd
pklC3H+tHM9t5C9owgP5MlK7JyBvGkkdHZhC8xSCGqc5+Y6ROj213fXGGRzQ03tl
f/757Wdd1vs=
=7qtO
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.