Red Hat Bugzilla – Bug 441313
[RFE] Set BootManager=None in /etc/kde/kdm/kdmrc
Last modified: 2008-04-10 08:56:20 EDT
Description of problem:
In KDE 3.5.9 (or up to kde-settings-3.5-38) the entry for "BootManager" is not
set. With KDE4 it is set to "BootManager=grub". So if you want to reboot from
KDM directly you have to choose which grub entry should be used after the next
IMHO this is a little bit confusing, at least if you update your system "in
the normal way". So there will always be two kernels listed (and maybe
the "Other" entry for Windows). But a normal user will maybe expect that a hit
on "Reboot" just reboot his machine
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make sure that there is more than one entry in /etc/grub.conf
2. Start kdm
3. Hit reboot
You have to choose one entry to actually reboot.
The machine just reboot.
This is also reported to cause issues with SELinux, though I can't find the bug
I'm against changing this (I added BootManager=grub on purpose). :)
You'll only see reboot options if you press-n-hold reboot button. Simply
clicking reboot will reboot into grub's default choice.
(In reply to comment #2)
> You'll only see reboot options if you press-n-hold reboot button. Simply
> clicking reboot will reboot into grub's default choice.
This behaviour is not working with KDE4's KDM anymore (at least for me/my
mouse) . Now I have to select an entry everytime. A short single click doesn't
worksforme. Wait, I see the opposite, I don't see any list of options on
press-n-hold anymore. ??
See also: https://bugzilla.redhat.com/show_bug.cgi?id=374011 for the SELinux
confirmed ok here with selinux=enforcing.
But, due to selinux policy (bug #373011), BootManager=grub doesn't work, so I
guess there's no point in trying to use it.
fixed in rawhide
* Thu Apr 10 2008 Rex Dieter <email@example.com> 4.0-18
- kdmrc: [Shutdown] BootManager=None (#441313)