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? -- evince assert failure: *** glibc detected *** evince: free(): invalid pointer: 0xb5abf8c9 *** https://bugs.launchpad.net/bugs/513261 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
