On Tue, Oct 2, 2018 at 1:17 AM, fedora2018q2@xxxxxxxxxxxxxxxxxxx wrote:
If a bug prevents booting, please propose it using the blocker review process. Unless it requires a really esoteric hardware setup, it's probably a blocker.
Hi Ray, unfortunately in some cases it doesn't though. It's currently completely breaking boot with amdgpu+LUKS, and before that for several months under amdgpu it was not echoing LUKS characters to screen or otherwise updating at all after showing the LUKS prompt, making it seem that password entry was not working and the boot process had frozen.
Since this is a very common setup, surely it should be a release blocker bug. I would propose it using the usual blocker review process.
In fact, since this bug looks like a disaster, I'm going to do that now.
I'm not jumping up and down demanding "devote all your time to fix my Plymouth bug(s)!" ;) (I've disabled RHGB for now on my system in any case); rather saying that if there aren't enough resources to make this level of maintenance realistic at the moment, it might be worth looking at whether it's still a good idea for Plymouth to continue to be enabled by default?
If a bug prevents booting, please propose it using the blocker review process. Unless it requires a really esoteric hardware setup, it's probably a blocker.
Michael
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
