[bug #46738] GRUB_DISABLE_RECOVERY in /etc/default/grub doesn't disable all recoveries

[redfast]

URL:
  <http://savannah.gnu.org/bugs/?46738>

                 Summary: GRUB_DISABLE_RECOVERY in /etc/default/grub doesn't
disable all recoveries
                 Project: GNU GRUB
            Submitted by: redfast00
            Submitted on: Mon 21 Dec 2015 03:58:24 PM GMT
                Category: Configuration
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: redfast00
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: 2.02~beta1
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

The following bug is also on
http://unix.stackexchange.com/questions/250587/grub-disable-recovery-not-working-on-detected-os

I have a laptop with a tripleboot of three Linux installs: Kali Linux 2.0 and
two times Debian 8.2 (one for gaming and one for development). I wanted to
disable the recovery options, so I uncommented `#GRUB_DISABLE_RECOVERY="true"`
in `/etc/default/grub`.

This succesfully removed the recovery options from Kali Linux (the system
where update-grub was run). However, this didn't disable the recovery options
for the two Debian installs. How can I disable the recovery options for the
two Debian installs without manually editing `/boot/grub/grub.cfg`?

Result of `cat /boot/grub/grub.cfg | grep 'recovery'` before uncommenting:

    menuentry 'Kali GNU/Linux, with Linux 4.0.0-kali1-amd64 (recovery mode)'
--class kali --class gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-4.0.0-kali1-amd64-recovery-1a2ddb7f-7fc3-40b5-b226-ed5cf940205e' {
        menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode) 
(on
/dev/mapper/ROOT--VG-DEBIAN--DEV)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64-root=/dev/mapper/ROOT--VG-DEBIAN--DEV
ro single-60442acd-d36a-4d7d-90c8-515281fe68d8' {
        menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode) 
(on
/dev/mapper/ROOT--VG-GAME--ROOT)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64-root=/dev/mapper/ROOT--VG-GAME--ROOT
ro single-1b27071e-4fcb-41c2-b9c8-01bccf90a10c' {
And after:

    menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode) (on
/dev/mapper/ROOT--VG-DEBIAN--DEV)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64-root=/dev/mapper/ROOT--VG-DEBIAN--DEV
ro single-60442acd-d36a-4d7d-90c8-515281fe68d8' {
        menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode) 
(on
/dev/mapper/ROOT--VG-GAME--ROOT)' --class gnu-linux --class gnu --class os
$menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64-root=/dev/mapper/ROOT--VG-GAME--ROOT
ro single-1b27071e-4fcb-41c2-b9c8-01bccf90a10c' {

If it matters, here is my disklayout:

 - /dev/sda1 mounted to /boot 
 - /dev/sda2 extended partition
    - /dev/sda5 lvm volume with ROOT-VG volume groum
        - /dev/ROOT-VG/GAME-ROOT
            - ext4 partition mounted to / in gaming machine
        - /dev/ROOT-VG/DEBIAN-DEV 
            - ext4 partition mounted to / in development machine
    - /dev/sda6 luks-encrypted volume
        - ext4 partition mounted to / in Kali Linux

Grub version: 2.02~beta2-22+deb8u1




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46738>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/