|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 Bootloader adds extra line to menu.lst | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | James Potter <jvc.potter> |
| Component: | YaST2 | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Minor | ||
| Priority: | P2 - High | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
menu.lst
menu.lst.old YaST2 logs Test package of perl-Bootloader for x86_64 menu.lst with new perl-Bootloader /boot/grub/menu.lst after changing default menu item /boot/grub/menu.lst before changing default menu item Yast2 logs during the change of default menu boot item |
||
Created attachment 214869 [details]
menu.lst.old
menu.lst before changes made by YaST2 Bootloader
Created attachment 214870 [details]
YaST2 logs
It seems to be problem of perl-Bootloader. Alexander could you check it please? Created attachment 216015 [details]
Test package of perl-Bootloader for x86_64
Hi James, could you please test with this package? Steps: - Install package with rpm -Uvh (maybe a --oldpackage is needed due to version) - Run YaST2 Bootloader again to try to reproduce the problem Thanks. Created attachment 216028 [details]
menu.lst with new perl-Bootloader
Since I left out the comment when adding the above attachment:
This bug is fixed!
On my Beta 2 system, I restored /boot/grub/menu.lst from menu.lst.old and then installed the new perl-Bootloader. (I didn't need --oldversion.)
Then I made the same edits that I made before but this time the extra configfile line was not added to menu.lst:
###Don't change this comment - YaST2 identifier: Original name: openSUSE 11.0 - 2.6.25-rc9-17 (/dev/sdb2)###
title openSUSE 11.0 - Beta 1 (/dev/sdb2)
root (hd1,1)
configfile /boot/grub/menu.lst
###Don't change this comment - YaST2 identifier: Original name: openSUSE 10.3 - 2.6.22.17-0.1 (/dev/sdb3)###
title openSUSE 10.3 - 2.6.22.17-0.1 (/dev/sdb3)
root (hd1,2)
configfile /boot/grub/menu.lst
Glad to hear that. This change is now submitted for openSUSE 11.0 and thus will appear with the next build. Closing the bug RESOLVED FIXED. Created attachment 230781 [details]
/boot/grub/menu.lst after changing default menu item
Created attachment 230782 [details]
/boot/grub/menu.lst before changing default menu item
Created attachment 230783 [details]
Yast2 logs during the change of default menu boot item
This bug fix did not make it into the released version of 11.0. I changed the default menu selection on OpenSUSE 11.0 (with KDE 4.0) and found that the extra configfile lines are still being added to menu.lst. I also found similar behavior with 11.0/KDE 3.5.9. I have not tried it with Gnome (nor Yast2-GTK) but, if the problem is perl-bootloader, I suspect that the results will be the same there. Reassigning to new maintainer. yes, problem was in perl-Bootloader, in lines cache lives old configfile section...so I remove it and every time recreate it. fixed in svn fixed in perl-Bootloader-0.4.69 |
Created attachment 214867 [details] menu.lst After using YaST2 Bootloader to rename one of the entries in my Grub menu.lst, an extra line was added to those menu items that booted old versions of openSUSE on other disk partitions. For example: title openSUSE 11.0 - 2.6.25-rc9-17 (/dev/sdb2) root (hd1,1) configfile /boot/grub/menu.lst became after editting the title: title openSUSE 11.0 Beta 1 (/dev/sdb2) root (hd1,1) configfile /boot/grub/menu.lst configfile /boot/grub/menu.lst Even an entry that was not changed had the configfile doubled: title openSUSE 10.3 - 2.6.22.17-0.1 (/dev/sdb3) root (hd1,2) configfile /boot/grub/menu.lst changed to: title openSUSE 10.3 - 2.6.22.17-0.1 (/dev/sdb3) root (hd1,2) configfile /boot/grub/menu.lst configfile /boot/grub/menu.lst There was no change to the default and failsafe entries, nor to either of the Windows entries in menu.lst. The doubled line does not appear to affect the booting process so this is only a minor bug.