Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Quoted
After installation
==================
After installation you have to set some variables allowing your system to find
KDE binaries and libraries and KDE to allow to find its own files, for Bash:
export QTDIR=~/kde3.5
export KDEDIR=~/kde3.5
export KDEDIRS=~/kde3.5
export LD_LIBRARY_PATH=~/kde3.5/lib
export PATH=~/kde3.5/bin:$PATH
Setting KDEHOME too, e.g. "export KDEHOME=~/.kdetest", will tell KDE to save
your settings to this directory and leave default ~/.kde directory unaffected.
On shadow password systems you have to set $(prefix)/bin/kcheckpass SUID root
or SGID shadow - otherwise you will not be able to unlock a locked desktop.
The complete KDE desktop is started with "startkde", most distributions start
it if you set it to the WINDOWMANAGER variable in your shell initializations.
I guess you don't have much of an imagination. The commands given in the documentation modify the environment for a Bourne-compatible shell and they reference the user's home directory. Where else could they possibly go?Quoted
Originally posted by coco-loco
I could not imagine that the bash-configuration has something to do with the launch of kde.
This post has been edited 1 times, last edit by "coco-loco" (Dec 4th 2005, 3:42pm)
Forum Software: Burning Board®, developed by WoltLab® GmbH
Linux Computer - Linux Forum -
Linux Computer und Notebooks - Lastminute - Wasserbetten & Whirlpools