Kile ⇒ kile PDFlatex build problem, after latest kubuntu update

[nikosd]

Running kile 2.1 on kubuntu, kernel 2.6.32-45-generic.
Always viewing pdf output in okular.
kile was running smoothly for a long time. With last set of updates, kile does not build PDFlatex anymore.

After trying to compile empty article file

Code: Select all

\documentclass[a4paper,10pt]{article}
\usepackage[utf8x]{inputenc}

%opening
\title{}
\author{}

\begin{document}

\maketitle

\begin{abstract}

\end{abstract}

\section{}

\end{document}

output produces following warning

Code: Select all

Cannot open log file; did you run latex?

Log file contents:

Code: Select all

*****
*****     PDFLaTeX output: 
*****     cd "/home/nikos/Desktop/kile-test"
*****     pdflatex -interaction=nonstopmode 'test-kile-2.tex'--shell-escape
*****
This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian)
entering extended mode
! I can't find file `test-kile-2.tex--shell-escape'.
<*> test-kile-2.tex--shell-escape
                                 
(Press Enter to retry, or Control-D to exit)
Please type another input file name
! Emergency stop.
<*> test-kile-2.tex--shell-escape
                                 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on texput.log.

Tried removing texlive, tex-common, and kile and reinstalling from command line, to no avail.

Different build methods work, for example LaTeX+DVItoPDF+ViewPDF produces proper pdf output.

What is going on?

[cgnieder]

The call seems to go wrong: it tries to compile a file called test-kile-2.tex--shell-escape (including the shell-scape). Unfortunately I don't know how the menu is called but you should be able to find some menu like "Configure Kile -> Tools -> Build" There you should find how the compiler is called. In case of PDFLaTeX it should be for command: pdflatex, and for options: -interaction=nonstopmode '%source'.

Regards

[nikosd]

Indeed, I looked in the build menu and the command being executed was
-interaction=nonstopmode '%source'--shell-escape
After removing the --shell-escape part, things run again.

No idea how the --shell-escape got there in the first place...

Thanks a lot,
Nikos