On Sat, Aug 17, 2019 at 6:25 PM Joseph D. Wagner <j...@josephdwagner.info> wrote: > > Sorry if this is the wrong place to post. I need to start somewhere. > > https://bugzilla.redhat.com/show_bug.cgi?id=1742953 > > Description of problem: > The Plymouth LUKS password prompt will wait FOREVER for me to type in a > password without powering down the monitor or blanking the screen. This > leaves me vulnerable to screen burn-in if 1) there was an unexpected > reboot like a crash, or 2) another OS (which shall remain nameless) > rebooted after update, but the dual-boot started in Linux instead of > the other OS. > > How reproducible: > 100% > > Steps to Reproduce: > 1. Wait at LUKS prompt until you need to throw away your monitor. > > Actual results: > A bill for an expensive new monitor. > > Expected results: > The monitor goes into powersaver mode after a reasonable time, like 20 > minutes, or at least blanks.
I wonder if systemd could provide a way for a service to ask for poweroff when a timeout has been reached, and for plymouth to set something like 20 minutes for the timeout? I agree that this shouldn't be an indefinite wait. Even consider a laptop scenario, we're going to wait until the battery completely discharges? That's not a good idea. -- Chris Murphy _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
