I got the update the other day and was unaffected by it.
I keep mine custom and so there is never a problem. All I see is this:
Code:
cavsfan@cavsfan-MS-7529:~$ grep -e "menuentry " -e "submenu" /boot/grub/grub.cfg | sed 's/^[ \t]*//' | cut -d "'" -f1,2 | nl --starting-line-number=0
0 menuentry "Precise Pangolin 12.04" {
1 menuentry "Precise Pangolin 12.04 (Recovery Mode)" {
2 menuentry "Quantal Quetzal 12.10" {
3 menuentry "Quantal Quetzal 12.10 (Recovery Mode)" {
4 menuentry "Raring Ringtail 13.04" {
5 menuentry "Raring Ringtail 13.04 (Recovery Mode)" {
6 menuentry "Saucy Salamander 13.10" {
7 menuentry "Saucy Salamander 13.10 (Recovery Mode)" {
8 menuentry "Linux Mint 13 Nadia" {
9 menuentry "Linux Mint 13 Nadia (Recovery Mode)" {
10 menuentry "Linux Mint 15 Olivia" {
11 menuentry "Linux Mint 15 Olivia (Recovery Mode)" {
12 menuentry "Windows 7" {
Or this: 20130529_110744.jpg
I did receive notification that /etc/grub.d/05_debian_theme and /etc/default/grub had changed and I took the newer versions of the files. I just made sure I edited them both before I rebooted.
The one thing that changed as far as this method of customization is that the font colors had to be moved to after line 117. As mentioned in this post.
The action of installing the updates installed grub on my Saucy install which is why I fixed it. I generally keep grub installed on another install besides the development version but have never had an issue when it was on that install.
Without customizing grub like when I initially install from an ISO the other installs are messed up even though I only have one swap file.
I generally just boot into Lucid, my main install which is usually in 640x480 instead of the normal 1900x1200 so I install grub there (sudo grub-install /dev/sda) and then reboot and put grub on which ever install I want it on.
Although it is fine to leave it on Saucy to avoid having to move grub around.
