On Thu, 23 Oct 2014 12:13:44 +0200 Peter Palfrader <wea...@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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
