Fails to save Grub configuration, after editing menu entry for Linux Mint

Bug #1569565 reported by RonCam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Grub Customizer
New
Undecided
Unassigned

Bug Description

I have customised the Grub2 menu for a triple-boot and all was well until I decided to 'clean up' the first line, for Linux Mint, by deleting the 'technical details' of where the installation is located, by removing all text following the letters 'KDE'. Have you any idea form your interpretation of the following error message as to why this caused the utility to abort without saving?

failed running 'grub-mkconfig -o "/boot/grub/grub.cfg"' output:
Generating grub configuration file ...
File descriptor 8 (/proc/3851/mounts) leaked on lvs invocation. Parent PID 9781: /bin/sh
  No volume groups found
Found Windows 7 (loader) on /dev/sda1
Found Windows 7 (loader) on /dev/sda2
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
Found linux image: /boot/vmlinuz-3.13.0-24-generic
Found initrd image: /boot/initrd.img-3.13.0-24-generic
error: syntax error.
error: Incorrect command.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 203
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
done

At this point, Grub Customizer appears to have crashed (unresponsive to attempts to close it) but I expect killing the process will do the job, without rebooting or restarting KDE.

Revision history for this message
RonCam (rac2) wrote :

Should have mentioned, I'm running --
LinuxMint Rosa 17.3 - KDE
Grub Customizer, most recent version, 5.0.5 .
and in this crashed condition, top shows 'kio_filenamesea' to be running and using 99.6% CPU.

After killing the above process and restarting the Customizer, the menu entry for Linux Mint is back to its 'pre-edit' (attempt) condition, and that is:
Linux Mint 17.3 KDE 32-bit, 3.13.0-24-generic (/dev/sda3)

summary: - Configuration fails to save, after editing the line for Linux Mint
+ Fails to save Grub configuration, after editing the menu entry for Linux
+ Mint
summary: - Fails to save Grub configuration, after editing the menu entry for Linux
+ Fails to save Grub configuration, after editing menu entry for Linux
Mint
Revision history for this message
RonCam (rac2) wrote :

Please, wait before spending any more time on this, because:

I just went back to the previous thread -- that I had stopped watching (sorry!) -- and saw that you completed it with an answer, as follows:

Sorry for late answer.
It's the same problem like here (with solution): https://bugs.launchpad.net/grub-customizer/+bug/1561813/

Thanks so much for continuing with my problem, and as soon as I post, I'll follow that link -- and probably solve the problem. If there's any further difficulty I'll continue here, or perhaps start a new thread.

Thanks again! :-)

Revision history for this message
RonCam (rac2) wrote :

I just went back to the previous thread -- that I had stopped watching (sorry!) -- and saw that you completed it with an answer, as follows:

Sorry for late answer.
It's the same problem like here (with solution): https://bugs.launchpad.net/grub-customizer/+bug/1561813/

Thanks so much for continuing with my problem, and as soon as I post, I'll follow that link -- and probably solve the problem. If there's any further difficulty I'll continue here ...

I did move the script, going up until it was at the first line, just above the submenu. Did I misinterpret the directions for the fix? There's still something wrong as I got this:

Please take a look at the command line output below. If you think this is a bug of Grub Customizer, please create one at https://launchpad.net/grub-customizer! Generally Grub Customizer should prevent errors like this.

failed running 'grub-mkconfig -o "/boot/grub/grub.cfg"' output:
Generating grub configuration file ...
File descriptor 8 (/proc/19028/mounts) leaked on lvs invocation. Parent PID 30488: /bin/sh
  No volume groups found
Found Windows 7 (loader) on /dev/sda1
Found Windows 7 (loader) on /dev/sda2
Found linux image: /boot/vmlinuz-3.13.0-24-generic
Found initrd image: /boot/initrd.img-3.13.0-24-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
Found linux image: /boot/vmlinuz-3.13.0-24-generic
Found initrd image: /boot/initrd.img-3.13.0-24-generic
error: syntax error.
error: Incorrect command.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 236
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
done

Does that give any clue?

Revision history for this message
Daniel Richter (danielrichter2007) wrote :

Please attach the new /boot/grub/grub.cfg.new

Revision history for this message
RonCam (rac2) wrote :

Thanks! I just saw your request.

Revision history for this message
Daniel Richter (danielrichter2007) wrote :

There's a submenu "Memory Tests -- Recovery Mode" containing:
 - Memory test (memtest86+)
 - Memory test (memtest86+, serial console 115200)
 - script code (!)
 - Linux Mint 17.3 KDE 32-bit, 3.13.0-24-generic (/dev/sda3)
 - Linux Mint 17.3 KDE 32-bit, 3.13.0-24-generic (/dev/sda3) -- recovery mode

You have to move the script code away from there.

Revision history for this message
RonCam (rac2) wrote :

Hi and please excuse the delay in replying -- I still want it to work, but 'other things' came up. I have taken your advice and added a bit to it. The line you marked with the '!' was moved up, our of the submenu.

Unfortunately it failed to save again. Since the idea seems to be, to 'clean up' the submenu, and I saw an 'Incoming Entries' line in the submenu, also, so I had the idea of moving that out of the submenu area, too.

Now the save succeeded, and the edits in the operating system names seems to hold.

It's a bit late here right now, so let me power down and see how things hold through a few reboots, tomorrow. I'll also do some checking to see if moving that 'incoming entries' line disabled anything from working normally, in the submenu.

Thanks again -- it was very nice to see a 'Save' go to completion

Revision history for this message
RonCam (rac2) wrote :

OK, thanks -- this thread may be closed. :-)

Moving that other line was a good idea.

Everything is fine on a reboot -- including entering into the submenu and highlighting the various options. I didn't go farther than that, but all should now be OK.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.