Tim,
In a standard non-graphical chroot, this is the path given from the Final Jaunty KDE3 x86_64 LiveCD when typing env:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
When typing which startkde, though it returns blank. Which is a problem.

In an Xephyr chroot(Graphical Chroot specifically launching /opt/kde3/bin/startkde) this is the path given from the Final Jaunty KDE3 x86_64 LiveCD when typing env:
PATH=/opt/kde3/bin:/opt/kde3/games:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/opt/kde3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin

In a standard non-graphical chroot, this is the path given from the Final Jaunty KDE4 x86_64 LiveCD when typing env:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
When typing which startkde, it returns:
/usr/bin/startkde

My suggestion from now on is to append the proper paths before building the LiveCD so that `which startkde` will return the proper path. I specifically introduced some code into the latest build of reconstructor(were hoping to release it soon) so that if `which startkde` fails, to use `which /opt/kde3/bin/startkde` so that it will recognize it is the KDE3 version of the LiveCD.

Btw, could you explain your build process for this? It's been awhile since we've last talked. Bootstrapped? :)

-Jon, red_team316




Hi Stefan,

Can you open /opt/kde3/bin/startkde and verify that the path is being set
with the /opt/kde3/bin directory?  Also, what do you get when you type env
into Konsole from a running KDE3.5 session?

Do you have more than one startkde installed (e.g. is this a KDE4
collision I didn't know about?)

Tim