Tom Wesley writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I've a feeling I'm going in circles here. Maybe time for sleep... But anyway, that doesn't work at all. I am using KDM though from kde2, but surely that won't affect anything. The settings from SOMEWHERE, and god knows I've tried everywhere should work. Is there something that can explain the order things get executed in SuSE from starting the xdm service to actually getting to the desktop. Or somewhere where I can read about it at least.
man X search for xsession. Here is a blurp: xdm (the X Display Manager) If you want to always have X running on your dis play, your site administrator can set your machine up to use the X Display Manager xdm. This program is typically started by the system at boot time and takes care of keeping the server running and getting users logged in. If you are running xdm, you will see a window on the screen welcoming you to the system and asking for your username and password. Simply type them in as you would at a normal terminal, pressing the Return key after each. If you make a mistake, xdm will display an error message and ask you to try again. After you have successfully logged in, xdm will start up your X environment. By default, if you have an executable file named .xsession in your home directory, xdm will treat it as a program (or shell script) to run to start up your initial clients (such as terminal emulators, clocks, a window manager, user settings for things like the background, the speed of the pointer, etc.). Your site administrator can provide details. <snip> Here is exactly what I have in mine: ~/.xsession # Suse stuff here ... # Towards the bottom ##################### # Start up kde3 beta export LD_LIBRARY_PATH=/usr/lib/qt3/lib:/opt/kde3/lib:$LD_LIBRARY_PATH export PATH=/opt/kde3/bin:$PATH WINDOWMANAGER=/opt/kde3/bin/startkde exec $WINDOWMANAGER