Le 29/02/2016 08:55, Steve Langasek a écrit : > On Mon, Feb 22, 2016 at 12:17:09PM -0000, Martin Pitt wrote: >> See also debian/patches/ubuntu-add-splash-option.patch which explicitly >> documents that plymouth should only be started with "splash". > > ... which appears to be a regression in xenial. The 'splash' commandline > option was previously used to control whether or not a graphical splash was > shown; it was *not* used to control whether plymouth itself was running, > only whether it was graphical. > > Didier, why have you disabled the plymouth services when 'splash' is not > given on the commandline? What is the expected boot experience now for e.g. > filesystem checks on a server (that may require interaction)? >
The argument passed from "splash" to "nosplash" in debian by default. I did try to reintroduce backward compatibility and this case handling. I may have missed some parts (reminder: 150+ files difference), and that was not the intend. Remember as well that the description is made from most of the diff I could understand. Indeed, even recent patches from people uploading plymouth in ubuntu included new patches without any description (and not following DEP3), which was making this merge even harder… We did try with Martin on a vm when a passphrase was asked from the start, and didn't see any issue, but that was maybe another case and we didn't get into that one. Feel free to amend and change for the expected user experience where the fundation team feel the needs. Cheers, Didier -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432265 Title: does not ask for LUKS passphrases without plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1432265/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
