Comment 67 for bug 477104

(Warning: English ISN'T my native lenguaje, so, please, be patient)

I'm affected by this bug too, but, in my particular case it appears when, before I install the "grub2-splashimages" package, I *also* make a modification of the "/etc/grub.d/05_debian_theme" in order to activate a splashimage, and later I execute the (now) (in)famous "update-grub2" and reboot.

Since yesterday, at 22:50, I was unable to access to my system until today, when I find this thread (¿it's correct to name it thread?). I follow the instructions of Zhmurov (#1) and 'Ta-Da', my system boot somoothly as I expect =D. I also follw the recomendation of make a 'full system update' and then 'exec' the 'update-grub2', but I make that yesterday so, I uninstall the kernel that I'm not using and then make the update of the grub. The result: nothing was changed, I still need to boot manually with the instructions of #1.

After 30 minutes of thinking (a miracle if I can say...) and reading all the posts (from #1 to #66), I started to look and try to understand ALL the files inside of '/etc/grub.d/', until I get the idea of restore the '05_debian_theme' that I modify yesterday (remember that Gedit makes a backup of the files), reboot the system and--- vouala! here I am, but this time the grub loads correctly.

I don't know if was an issue of the splashimage or an issue of syntaxis in the '05_debian_theme' file, but I want to know what was the problem and in which way that files (all the files in /etc/grub.d/*) affects in the load of the grub, and I don't know if that little discovery could help to someone here (I hope that it can).

Any way, I'm still looking around about a final solution of this bug.

Long days and pleasant nights...