Bugzilla – Bug 847743
Outdated GRUB 2 entry name after upgrade from 12.3 to 13.1
Last modified: 2018-02-21 22:58:55 UTC
Created attachment 565094 [details] y2logs User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 I have just upgraded my laptop from 12.3 to 13.1 RC1 using a pen drive (DVD image). After the upgrade, the GRUB 2 entry remains the same ("openSUSE 12.3") instead of being updated to "openSUSE 13.1" JFYI, I can boot fine into 13.1 RC1 and I'm not dual-booting. Reproducible: Always Steps to Reproduce: 1. Upgrade from 12.3 to 13.1 RC1 2. Check GRUB 2 menu entry Actual Results: GRUB 2 menu entries are out-dated (openSUSE 12.3) Expected Results: GRUB 2 menu entries should be updated (openSUSE 13.1)
Created attachment 565095 [details] GRUB config file
Note: I haven't tried to reproduce it. If this happens to you as well, please confirm it. Thanks!
Hi Javier, This is known problem, please follow this ML discussion to set a new version. http://comments.gmane.org/gmane.linux.suse.opensuse.devel/53785 The reason why it's not updated is because that's user editable thus we won't touch in case overwriting it which could be arbitrary strings .
Thanks for telling, Chang. I see your point. It's user editable. However, I think we could solve it by using a script to check if it has been modified by the user or not (ie: the entry is openSUSE 12.3) to update it (ie: to openSUSE 13.1).
Agree with comment #4.
Much as I hate "chiming in" with "me, too," in bug reports, as there is no voting system enabled here, I would add my support for Javier's comment #4. I just bumped from 13.1 to 13.2, and was somewhat taken aback when my boot menu still said 13.1 (was my upgrade broken?). As an engineer, I'm not really rattled by such things, and I was aware that my zypper dup all looked fine (and I do know how to manually edit /etc/default/grub). Still, it seemed oddly un-polished for this to be left undone.
We are now handling this on bsc#956660. *** This bug has been marked as a duplicate of bug 956660 ***
*** Bug 848801 has been marked as a duplicate of this bug. ***