Hello,

I have problems to understand the way kile is accessing the PATH-Variable using Ubuntu (natty). I am not sure, if it is an kde, kile or ubuntu issue.

Problem details:
* We have an modificated TeXLive2010-Environment. A special directory contains the environment and we usually set the bin-path of the modificated TeX-Environment to the begin of PATH -- it works fine with CentOS 5.x, even if we have the distribution texpackage installed at the same time to solve the package dependencies issues.

For all cmdline-Tools and most editors it works the same way on Ubuntu, except for kile.

The kile systemcheck itself shows no problem. All binaries of our modificated tex-environment (e.g. /Applic/tex/bin/pdflatex, not /usr/bin/pdflatex) are detected and preferred. Kile uses the PATH-Variable as expected.But when we push the compile button, kile uses the ubuntu-distribution-version, that should not be used if kile would use the PATH-Variable:

~/usr/bin:/Applic/tex/bin:/usr/bin.....

Strace shows that kile looks -- when compiling a document -- for "/usr/lib/kde4/libexec/pdflatex" and "/usr/bin/pdflatex" always BEFORE the first element of the PATH variable is progressed.
Usually kile finds pdflatex in /usr/bin, the result is that our own version, that should be preferred by PATH-Environment, is not used.

If we change our kile settings to use an abolute path, it works -- but this would create a lot of problems for us.

The different behaviour of systemcheck and pdflatex-compile makes me thinking about a bug or a configuration file I am not aware off.

I am unsure, if this is kde, kile or ubuntu related issue.

Any ideas are greatly appretiated.

HansiSolo

This is probably a bug if Kile is checking it's own paths before moving on to those in $PATH. I would suggest filing a bug on it's tracker and using the hardcoded name in the interim.