Bug#279042: Bug#273789: tetex-base: fmtutil.cnf not found

[Frank Küster <frank@debian.org>]

Hilmar Preusse <hille42@web.de> wrote:

>> 
>> strace -o xdvi.trace xdvi
>> 
> I wouldn't do it that way. There is the shell program, which sets
> some ENV variables IIRC. I think it's a better idea to copy
> /usr/bin/xdvi into the home dir, edit it appropriatly and then call
> it typing "./xdvi filename".

Uups, I forgot that. But I would suggest a different approach:

1. First, find out whether it needs a filename to get the error, as
   described before

2. Then, find out whether the error also occurs when xdvi.real is called
   directly: 

/usr/bin/xdvi.real $filename; echo $?

   or just

/usr/bin/xdvi; echo $?

   depending on the outcome of the test in 1. The error message will be
   different, perhaps there will be no message at all. But the echo
   command will display "0" if everything is o.k., or a different number
   if something went wrong

3. If you still get an error, do

strace -o xdvi.trace /usr/bin/xdvi $dateiname.dvi 

  (or without the filename) and send us xdvi.trace.

Regards, Frank
-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer