Version: 1.4 (using KDE KDE 3.5.6) Installed from: SuSE RPMs Compiler: gcc 3.3.5 (SUSE Linux) OS: Linux On some files (presumable using virtual fonts like "kcmr10") "kdvi" enters an infinite loop while trying to display the first page. The system nearly freezes due to expansive usage of CPU and it continues till "kdvi" fill the whole swap space (I checked it by starting "top" before "kdvi") and finally is killed by the system. If I start "kdvi" from a K-application the application starting it is also killed. Been started from "xterm", "kdvi" produces no output after opening the dvi-file.
Created attachment 20350 [details] An example of a file causing the crash I suspect that the cause of the crash is the cyrillic fonts like "kcmr10" using the virtual fonts (.vf) technology. These fonts are part of the package "CTAN:/fonts/cyrillic/cmcyr" by N.Glonty, A.Samarin, B.Malyshev. Note that "xdvi" has no problems with these fonts.
I had the same problem but its not related with kdvi itself but I think it is related with the Ghostscript. Check if your problem is the same in this thread: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/114866 I solved my problem following this tips: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/114866/comments/5 P.S. - It happens to me with documents with EPS figures.
I do not think so. I have no problem with looking with "gv" the file generated from my dvi file by "dvips". I have no problem with "xdvi". I have just checked the file with "kdvi" from KDE 3.5.5 from the distribution OpenSuSE 10.2 I use now. It does not go into an infinite loop but crashes with "Segmentation fault".
Just now I tried "kdvi" from the package "kdegraphics3-tex-3.5.10-2.28.rpm" (under SUSE 10.3). Now kdvi chashes (Segmentation violation) on the files with virtual fonts.
kdvi is no longer maintained since KDE SC 4, and its functionality is replace by okular. If the issue in this report still exists in or apply to okular in KDE SC 4.10.5 or higher, please reassign the report to okular product or create a new report against okular.