I'd like to point out a couple of things that were lost when my bug was merged with this one:
1. This bug happens every time a distribution upgrade of Ubuntu comes out. It's been happening since Warty, and I've had to report the problem and wait a couple of months for a fix every time. 2. Every time this happens you guys are utterly surprised like you've never seen anything like it, and you poke and prod at the people reporting the bug to try a bunch of different configuration changes to see if they can fix the problem themselves. That is not acceptable behavior. This creates a number of problems: 1. You're treating Ubuntu like it's Joe Distro, your average linux distribution that is thrown together by some bored computer nerd in their basement for fun in between raids in World of Warcraft, or whatever game it is kids are playing these days. But the reality is that Ubuntu ships on hardware from OEMs. Actual, real computers and embedded systems that people buy and expect to work. So when a problem like this happens to the average user who is not technically astute in troubleshooting a complex operating system, this means that a bunch of people are going to restart their computer and go "huh, I can't log in. I enabled encryption and now my computer doesn't work. I don't trust this OEM anymore." 2. This is a repeating, critical problem. This isn't a problem that prevents you from browsing the web or from playing games, it completely disables access not only to your operating system but to all of your files as well. How you guys can see this happen once and not have some process in place to check that it doesn't happen with the next build is beyond me; how you can let it happen every single time there's a new version out is preposterous. For every Ubuntu user who reports this problem there are hundreds who don't understand what's going on and just think their computer is broken. How are they even supposed to use ubuntu-bug if their computer won't start? This should be a P0 bug because anyone who experiences this problem has a critical issue but you're treating it with the same level of importance as a minor inconvenience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386005 Title: Password not accepted graphical boot for encrypted root system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1386005/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
