Hello again I'm currently looking at plymouth source code and trying to find a solution to elegantly solve the issue mentioned in this bug at the plymouth level, as Steve Langasek suggests.
Unfortunately, I'm wondering whether this can be achieved. Plymouth seems to be totally agnostic of where client requests come from (except to know where to send replies back) and to what purpose (and thus can not know anything of the logic which may bind some requests to others). Am I right in this regard? This means that one could improve the handling of "interactive" requests that depend on keyboard input (password prompt, question, waiting for keystroke) and avoid to display the corresponding prompt message as long a preceding "interactive" request is still unanswered (or not canceled). This is possible (and already dealt with at some level) because keyboard input can only match the latest pending request. BUT I don't see how one could filter out messages to be displayed based on other "interactive" requests. While plymouth should not display mountall "boredom" messages while cryptsetup is waiting for password input, I'm sure there are existing use cases where messages from one client must be displayed regardless of the "interactive" request(s) of other(s). How can plymouth tell the difference? Thank you for your replies Cédric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104156 Title: "Continue to wait, or Press S to skip mounting or M for manual recovery" when waiting for LUKS passphrase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1104156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
