Slack 10.1: Booting KDE

JRR883 · 08-27-2005, 03:01 PM

I just installed Slackware on /dev/hda5 (dual-booting with WinXP Pro). I can't get Lilo to run at boot, so I'm having to boot with the bootdisk I made during installation. I do that, login as root, and I have a prompt, something like darkstar@slackware, I'm sure you know what I'm talking about. What is the command to boot into the KDE GUI?

Also, how would I get Lilo installed? I had it installed during the installation process, but it won't load during bootup, as mentioned before.

tuxrules · 08-27-2005, 03:14 PM

Make a regular user first with the adduser command. After that you can login as regular user. As you might know, logging in as root is not advisable for number of reasons.

After adding a regular user, you can issue the following command to start kde

Code:

startkde

For lilo, you can login as root and issue the following command

Code:

liloconfig

and don't forget to install it on /dev/hda (or whatever is your primary master hard drive)

-Tux,

You can also edit /etc/inittab file and look for line

Code:

id:3:initdefault:

Change that "3" to "4" and you will get a graphical login (like gdm, kdm or xdm). I believe you would have to configure the default graphical login.

JRR883 · 08-27-2005, 04:03 PM

Okay, I have Lilo installed properly: thanks for that. I tried startkde and it gave me this:

Code:

kde-config: error while loading shared libraries: libart_lepl_2.so.2: cannot open shared object file: no such file or directory
/opt/kde/bin/start kde: line 138: xset: command not found
/opt/kde/bin/start kde: line 141: xset: command not found
/opt/kde/bin/start kde: line 144: xset: command not found
/opt/kde/bin/start kde: line 154: xsetroot: command not found
startkde: Starting Up...
kreadconfig: error while loading shared libraries: libart_lgpl_2.so:cannot open shared object file: no such file or directory
ksplash: error while loading shared libraries: libart_lgpl_2.so:cannot open shared object file: no such file or directory
kdeinit: error while loading shared libraries: libart_lgpl_2.so:cannot open shared object file: no such file or directory
startkde: Could not start kdeinit. Check your installation.
/opt/kde/bin/startkde: line 207: xmessage: command not found
Warning: connect() failed: : no such file or directory
ksmserver: error while loading shared libraries: libart_lgpl_2.so.2: cannot open shared object or file: no such file or directory
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
/opt/kde/bin/startkde: line 232: artsshell: command not found
startkde: running shutdown scripts...
startkde: Done
user@darkstar:~$

Any suggestions?

JRR883 · 08-30-2005, 12:54 AM

Bump, this issue is pissing me off.

Also, I cannot use the startx command. It says it's not a valid command, which is total bullshit. Should I just reinstall the packages?

Hangdog42 · 08-30-2005, 07:08 AM

Did you run xorgconfig after you installed Slackware?

reddazz · 08-30-2005, 09:53 AM

When you have configured your xserver, you may also need to run "xwmconfig" and select KDE as your default desktop so that an .xinitrc or .xsession file is created which will start KDE correctly.

JRR883 · 08-30-2005, 04:27 PM

I ran xorgconfig and the command was not found. I ran xwmconfig and selected KDE as default, as I had before, and when I ran startkde it gave me the same error log.

Hangdog42 · 08-30-2005, 04:52 PM

Quote:

I ran xorgconfig and the command was not found.

Were you root when you ran this command? If you didn't run it after install, you're not going to get X to work until you do. It should be in /usr/X11R6/bin.

JRR883 · 08-30-2005, 04:55 PM

Yeah, I was in root. Still didn't work.

nadroj · 08-30-2005, 05:00 PM

login as root and try xorgconfig again

edit: lol whoops too slow. disregard then.

titopoquito · 08-30-2005, 06:11 PM

I guess you logged in as normal user and switched then with su to become root. In this case you might not get the right PATH settings, so that commands in /usr/X11R6/bin are not found. You can either log in as root from the beginning (right after booting up when the first login appears) or you could execute the commands with the right path, for example type /usr/X11R6/bin/xorgconfig to get it started

Edit: To make it clear, xwmconfig and startx also reside in the same directory /usr/X11R6/bin, so to start them you would have to do the same and type them in with the path before them. If you cannot start the "startx" command as normal user look for "PATH" here on linuxquestions, you will find many threats on it and how to add additional directories to it. You could just look at the file /etc/profile for this. This is where the PATH is defined systemwide.

reddazz · 08-31-2005, 04:36 AM

Quote:

Originally posted by JRR883
I ran xorgconfig and the command was not found. I ran xwmconfig and selected KDE as default, as I had before, and when I ran startkde it gave me the same error log.

You need to run "startx" and not "startkde" when you xserver has been configured and you have chosen KDE as your default desktop afer running "xwmconfig".