Here's the output from using the 'startkde' command. But I should tell you that I get the same output with the official qt-3.3.1 Slackware package: [code:1]xset: unable to open display ""
xset: unable to open display ""
xset: unable to open display ""
xsetroot: unable to open display ''
startkde: Starting up...
ksplash: cannot connect to X server
kdeinit: Aborting. $DISPLAY is not set.
Warning: connect() failed: : No such file or directory
ksmserver: cannot connect to X server
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
startkde: Done. [/code:1]
First, I'm running in runlevel 4, not runlevel 3, so when I go to tty1, I cannot enter anything since KDE is started automatically. There is no command prompt............The only other console available, which I can log in to, is Alt-F6.
I logged into that one, removed the official qt pkg, installed my compiled qt pkg, and then ran 'startkde', which gave the me the above output.....................However, after removing my pkg and reinstalling the official pkg, I ran 'startkde' and got the same output above, yet I can start the gui using the command 'kdm'........................The command 'kdm' doesn't give me any messages of any kind on the console......
This problem has the exact same symptons that would happen if there are any missing startup files for kdm in the /opt/kde/share/config/kdm directory................that is, you start with a login screen, but when you try to log in, the screen blacks out momentarily, then you are presented with the login screen again....
How long a minute is depends on which side of the bathroom door you're on.