Ubuntu
evince package

  1. Bug #513261
  2. Comment #9

Comment 9 for bug 513261

Revision history for this message
fiat1100d (gratteri-email) wrote :

I noticed the same behaviour reported by Lucian:
- evince crashes when opening DVI without Valgrind;
- it displays fine when slowly opening DVI using Valgrind;
- after that the same DVI document still opens correctly when running without Valgrind.

From the debugger logs, I see that the ~/.texmf-var directory is used for generating fonts.
If I try to delete ~/.texmf-var (rm -r .texmf-var from Home directory) after the above passages, and then run evince for opening the same DVI document, it crashes again. But, if I run evince with Valgrind, then the document opens fine as in the above mentioned steps.

Lucian, could you check this?