Have a look at probably simpler solution provided here: https://bugs.launchpad.net/cryptsetup/+bug/556372
The solution is to install plymouth-dummy package and remove the standard one. Then everything works fine as earlier. This is fully based on https://bugs.launchpad.net/cryptsetup/+bug/556372/comments/78 ### Oliver Joos (oliver-joos) wrote on 2012-03-25: #78 Ok then, here is the ready-to-install plymouth-dummy_1.0_all.deb! It's an empty package but allows to remove plymouth while keeping the packages that have wrong dependencies to plymouth. To workaround this (WontFix??) bug and remove plymouth just execute 2 commands in a Terminal: sudo dpkg -i plymouth-dummy_1.0_all.deb sudo apt-get remove plymouth Advanced users can build plymouth-dummy_1.0_all.deb themselves: see comment 16 Many thanks to Christian Kujau! ### I've tested it on 12.04 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595648 Title: Remote unlocking not possible if plymouth is active (Bug or Feature?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/595648/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
