On Wed, Dec 10, 2014 at 12:28 PM, Matthias Klumpp <m...@debian.org> wrote: > 2014-12-10 15:51 GMT+01:00 Felipe Sateler <fsate...@debian.org>: >> [...] >> Other information that may be relevant: >> >> When installing gdm3, the following message is displayed: >> Setting up gdm3 (3.14.1-3) ... >> WARNING: /lib/systemd/system/kdm.service is the selected default >> display manager but does not exist >> Job for gdm.service failed. See 'systemctl status gdm.service' and >> 'journalctl -xn' for details. >> invoke-rc.d: initscript gdm3, action "reload" failed. >> >> >> Masking gdm3 resulted in a booting system. This is strange because >> failure to boot with gdm3 masked is what prompted me to unmask the >> service and discover this problem :/ >> >> >> Any other information I can provide, please let me know > > Hey there! > This *might* actually be a Plymouth bug. We work around that in > Tanglu, but upstream is working on a better patch. > If you know how to patch Debian packages and rebuild them, you could > try to apply the patch in > https://bugs.freedesktop.org/show_bug.cgi?id=73585 > to Plymouth and see if that fixes it. If so, wait for a proper patch later ;-) > Note: There might still be a systemd-unit issue, but the description > of this bug looks very familiar.
I applied the patch, and it did not fix the issue. This bug report looks a lot like #766462 , so it should probably be merged with that one. The problem is that I do not know which package it should be assigned to. Probably plymouth, but I'll let either maintainer decide. -- Saludos, Felipe Sateler _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
