Function Lock setting is not saved after cold boot
The problem you're addressing (if any)
The function lock setting is not saved after shutting down the computer and cold booting it.
Describe the solution you'd like
Save the function lock setting after shutting down the computer so that the user does not have to re-enable it after booting back the computer.
Where is the value to a user, and who might that user be?
When the function lock setting is enabled before shutting down the computer, it must stay on after cold booting the computer so that the user don't have to re-enable it after logging into his account.
Describe alternatives you've considered
None.
Additional context
Feature request for NovaCustom NV40MZ (Tiger Lake variant) running GNOME and Arch Linux.
Maybe putting a switch in the computer's UEFI to save the state of the setting : "Save Function Lock State : Enabled / Disabled" or "Always enable function lock : Enabled / Disabled"
Apologies for no reply since then on this issue. Thanks for reporting this issue. We have not planned such feature so far, but we will definitely consider it and update here whether any plans has been made.
@BeataZdunczyk we should at least take another look and see how big of an effort it would be to implement.
On NV41PZ (ADL), on v1.8.0-rc3, the Fn Lock is persistent across normal warmboots. Performing a coldboot by disconnecting the battery pack does make it return back to off.
I wonder if the coldboot in question wasn't supposed to mean a normal shutdown. In that case the Fn Lock is persistent across normal shutdowns unless one opens the backplate and disconnects the battery.
Ok, removing the ADL model labels then. We will still need to reproduce the issue on TGL with the next release before closing this issue.