https://bugzilla.novell.com/show_bug.cgi?id=850531
https://bugzilla.novell.com/show_bug.cgi?id=850531#c28
--- Comment #28 from Raymond Wooninck
I'm aware that kdm does work similar as plymouth_quit() function in /etc/init.d/xdm but more smooth one as seen from the patch you've linked to.
Each DM has its own pros and cons. I know that KDM is not one of the best for the smooth transition as that a full black screen is shown before the KDM login screen is shown. GDM is handling this better, but I guess that we are then starting to talk about KDM internal procedures, etc and not about plymouth specifics. As indicated upstream recognized that KDM is actually not really maintained anymore and the KDE Framework 5 releases will no longer have KDM there. Actually the KDM sources have already been deleted from upstream.
The question is: wouldn't it better to stop plymouthd before any dm is started. And still to see the smooth transion on vt7 to start the daemon spawned by the plymouthd executable on vt7?
How many effort would it be to implement this by using the ply_terminal_activate_vt() before the daemon will be forked ?
Question for me is what are we trying to solve here ? What is the real bug behind this all ? The original bug was that upon shutdown the login screen was shown. Which happens to me also from time to time and that always happens after some updates. This is something that is not plymouth related, as already indicated by me, as that it also happens without plymouth installed. The KDE workspace issues the shutdown command and that is interrupted as that it appears that the user no longer has the authority to shutdown the system and therefore the system returns to the login prompt. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.