Re: Laptop powerdown when early boot incl. bootloader phase stuck (Was: Bug 1742953 - No Screensaver/Powerdown after Inactivity at LUKS Password Prompt)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday, August 23, 2019 4:46:53 AM MST Jan Pokorný wrote:
> On 20/08/19 20:59 -0600, Chris Murphy wrote:
> > There is no good reason for the current behavior, in particular on a
> > laptop. And it's fail danger, not fail safe. The very simple work
> > around for the computer shutting off in 3 minutes of inactivity and
> > you don't like that? Power it back on and enter your passphrase.
> > Shockingly easy and obvious. Unless of course you're stuck somewhere
> > and in fact want to use your laptop as a heating pad.
> 
> Just that the particular corner case is not perceived in isolation,
> there are other early-boot-stuck situations that would make sense
> to deal with in the same fashion even if the sources are completely
> different (predictability is more important from user's POV, IMHO).
> 
> One such other situation is having the bootloader (grub2) failed and
> hence be stuck in 'press a key to continue' or just staying in the
> selection menu without any timeout ticking for whatever reason.
> That's directly comparable to the LUKS prompt without any attention
> for a prolonged time.
> 
> With grub2, situation is actually worse, since without having any
> means to control CPU throttling (which is already present by the
> time one is to enter LUKS password), laptop will indeed become
> said "heating pad" after a bit (one could for instance enter the
> grub prompt if it's deemed a feature for some).

To clarify on this a bit, GRUB will only stat "in the selection menu without 
any timeout for whatever reason" if it is either not configured to 
automatically select an entry after a timeout, or a key is pressed before the 
timeout, meaning GRUB expects you to choose a different boot option.

As for "stuck in 'press a key to continue'", if it didn't do this, you would 
have no way of knowing what the error is to recover your system.

-- 
John M. Harris, Jr. <johnmh@xxxxxxxxxxxxx>
Splentity
https://splentity.com/

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux