Bug 10221

Summary:	kcm-grub2 fails to run grub2-mkconfig when saving settings
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	fundawang, shlomif
Version:	3	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kcm-grub2-0.5.8-4.mga3.src.rpm	CVE:
Status comment:

Description Barry Jackson 2013-05-22 13:31:13 CEST

Description of problem:
After  editing settings in kcm-grub2 the "apply" triggers an error dialog with:

#----------
Command: /sbin/grub2-mkconfig /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
Error code: -2
Error message:
The process could not be started.
#----------

The changes are applied correctly to /etc/default/grub, so a workaround is to close kcm-grub2 after receiving the error and manually run update-grub to 'apply' the new settings. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2013-05-24 20:20:36 CEST

Keywords: (none) => Triaged
CC: (none) => fundawang, shlomif

Comment 1 Marja Van Waes 2015-03-31 16:07:04 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD