Starting other OSes thru KDE's "Restart Computer" button
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Starting other OSes thru KDE's "Restart Computer" button
KDE will allow you to start other OSes via its "Restart Computer" button, if you have GRUB installed (or LILO) and select your boot manager in the KControl > Login Manager > Shutdown > Boot Manager dropdown list. For some reason, it's not working on my computer, although GRUB's set up and working just fine, and it displays the choices I could make.
Did anyone have a similar problem, and how did you fix it? It works fine in PCLinuxOS on another box. I don't see any special GRUB section or "kdmrc" section that governs this.
(On an unrelated, uh, note, it looks like the "alsaconf" utility is now broken, as of today's dist-upgrade of Lenny. Fortunately, sound still works fine.)
Not an answer, but I'm having the same problem on Fedora 7 after the latest KDE upgrade. So I'd suspect a KDE problem rather than a Debian one.
Oh, I presume you're using KDE as you display manager. (Fedora defaults to using GDM instead of KDE. I know nothing about the Debian defaults, so I thought I'd ask.)
Did anyone have a similar problem, and how did you fix it?
Yep a while ago. If I remember correctly I had to change grub's menu.lst. More specifically the "default" option, usually it's set to "default 0". Change it to read "default saved".
In Debian testing, if you install both Gnome & KDE, GDM will be the default display manager. To get KDM as the display manager I install a bare bones system (select only "standard system" in tasksel), then add the x-window-system, kde-core, kdm, libgnome2-perl, gnome-system-tools, synaptic, hal, pmount, usbmount, alsa, alsa-utils, mozilla-firefox and mozilla-thunderbird (which installs the ice rodents).
Last edited by Junior Hacker; 07-27-2007 at 08:30 PM.
Yep a while ago. If I remember correctly I had to change grub's menu.lst. More specifically the "default" option, usually it's set to "default 0". Change it to read "default saved".
Yes, that did it. Now to change "timeout 15" to "timeout 5" and be happy with it. Thanks.
(For some reason, PCLinuxOS manages to do this when you manually choose the OS, both without using "default saved" (it has "default 0"), and without waiting the defined timeout period. Maybe this has something to do with its version of grub.)
<edit> By the way, if you've already got both kdm and gdm installed (try "apt-get install kdm" if you don't, and let Debian take care of the dependencies) and you want to change display managers, it's as simple as running
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
