I had the same experience as #8 and #9.
Some hours wasted troubleshooting why the kernel didn't have expected options, only to find "curtin the culprit", which led me to this bug report.
Here's the kicker - I didn't even have curtin installed! Why is the config file still present on the system?
# dpkg --list '*curtin*' dpkg-query: no packages found matching *curtin* # dpkg -S 50-curtin-settings.cfg dpkg-query: no path found matching pattern *50-curtin-settings.cfg* # # grep curtin /var/lib/dpkg/info/* # ls /etc/default/grub.d/50-curtin-settings.cfg /etc/default/grub.d/50-curtin-settings.cfg
I suggest 'update-grub' at least report when variables are overrriden and where.
I had the same experience as #8 and #9.
Some hours wasted troubleshooting why the kernel didn't have expected options, only to find "curtin the culprit", which led me to this bug report.
Here's the kicker - I didn't even have curtin installed! Why is the config file still present on the system?
# dpkg --list '*curtin*' settings. cfg settings. cfg* dpkg/info/ * grub.d/ 50-curtin- settings. cfg grub.d/ 50-curtin- settings. cfg
dpkg-query: no packages found matching *curtin*
# dpkg -S 50-curtin-
dpkg-query: no path found matching pattern *50-curtin-
#
# grep curtin /var/lib/
# ls /etc/default/
/etc/default/
I suggest 'update-grub' at least report when variables are overrriden and where.