Bug 907965

Summary: boot option in kde menus is permanent
Product: [openSUSE] openSUSE Distribution Reporter: Jean-Daniel Dodin <jdd>
Component: BootloaderAssignee: Jiri Srain <jsrain>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: wbauer
Version: 13.2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jean-Daniel Dodin 2014-12-02 10:03:17 UTC
sorry, I don't know how to classify this, buts it's very annoying. I had the same problem years ago, may I'm the only one to use this option :-).

The bug is critical only if you use the option.

I speak of the ability to choose the next starting system directly from the close menu in kde4 or kdm, here in 13.2.

In fact the choice is not for the next reboot, but permanent. In my case, I choosed to start the old 13.1, and the computer started then 13.1 with no other choice, at any reboot.

It became impossible to boot any other system.

One can just see the upper left flashing "grub" starting message.

To fix this, I had to go to the bios start menu, choose the other disk 13.1 is installed in to get the 13.1 menu (for what ever reason 13.1 do not see 13.2 boot), enter the grub console, load the kernel, the initrd and then I could bring up the 13.2 standard boot, and in kdm choose the "opensuse" normal option.
This seems to reset the system to normal working state (I hope so :-).
The problem sits somewhere in the grub2 config file.
Comment 1 Jean-Daniel Dodin 2014-12-02 10:33:03 UTC
in fact the solution I described do not works, it simply change the unattended boot option. To have back the grub menu I had to reset grub with yast (I coudn't indentify thye problem in grub.cfg)
Comment 2 Wolfgang Bauer 2014-12-02 12:51:14 UTC
This is because grub2 cannot write to btrfs partitions and therefore cannot reset the entry to boot.

To "fix" it, remove /boot/grub2/grubenv manually.

A workaround to prevent the problem would be to remove those lines from /etc/grub.d/00_header:
cat << EOF
if [ -f \${config_directory}/grubenv ]; then
  load_env -f \${config_directory}/grubenv
elif [ -s \$prefix/grubenv ]; then
  load_env
fi
EOF

grub2 would then just ignore grubenv.

Or use a separate /boot partition, formatted in ext2 e.g.

*** This bug has been marked as a duplicate of bug 856391 ***
Comment 3 Jean-Daniel Dodin 2014-12-02 13:43:33 UTC
thanks...