A possible fix for observed kernel start failures after using the no-UI autoshutdown widget sample: Instead of partially installing the package to disable the extension UI, fully install it but disable the UI.
This is not ideal because the result is that the full extension UI is installed but de-activated (e.g. if users enabled and then opened the extension manager they could potentially find and enable the auto-shutdown settings UI) - but seems to solve the error and I think doesn't materially change the likelihood of users finding & disabling/editing the settings? It also has the nice consequence that we're not trying to hack around partially installing the package.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: N/A
Description of changes:
A possible fix for observed kernel start failures after using the no-UI autoshutdown widget sample: Instead of partially installing the package to disable the extension UI, fully install it but disable the UI.
This is not ideal because the result is that the full extension UI is installed but de-activated (e.g. if users enabled and then opened the extension manager they could potentially find and enable the auto-shutdown settings UI) - but seems to solve the error and I think doesn't materially change the likelihood of users finding & disabling/editing the settings? It also has the nice consequence that we're not trying to hack around partially installing the package.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.