should collect /etc/default/grub from package install failures due to update-grub failing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
High
|
Brian Murray | ||
Precise |
Fix Released
|
High
|
Brian Murray |
Bug Description
[Impact]
Apport does not inclue an important configuration file for determining the root cause of errors for some package installation failures. Since the majority of our bug reports come from stable releases it would be good to release the update to apport to Precise. Additionally, if we ask people to manually add /etc/default/grub they would have to manually remove any username and password infromation from it. Instead with the apport hook it is done automatically.
[Test Case]
1) Modify /etc/default/grub by removing the final " from the quiet splash line so you have "quiet splash instead of "quiet splash".
2) Execute apt-get install --reinstall memtest86+
3) Observe package installation failure
With the version from -proposed there should be an attachment called EtcDefaultGrub which contains the contents of your /etc/default/grub file. You will see this in the resulting apport dialog.
[Regression Potential]
Its possible that something is wrong with the regular expression that searches DpkgTerminalLog and we won't actually receive /etc/default/grub. However, this is working in Quantal so is unlikely.
Package installation failures frequently happen due to configuration errors in /etc/default/grub which are encountered when running update-grub. It'd be good if apport would to collect /etc/default/grub using attach_default_grub from hookutils.py to collect this file so we can see what Ubuntu users are doing wrong.
Here's a patch to add in the information for precise's version of apport.