Bug 109129

Summary: kdvi is not showing the .dvi files correct
Product: kdvi Reporter: Dragomir Deltchev <drago>
Component: generalAssignee: Stefan Kebekus <kebekus>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Dragomir Deltchev 2005-07-15 12:03:54 UTC
Version:           1.7.1 (using KDE 3.4.1-0.fc4.1 Red Hat, Red Hat Linux (Stentz))
Compiler:          Target: i386-redhat-linux
OS:                Linux (i686) release 2.6.11-1.1369_FC4

kile is working good accept, when i try to view the .dvi file the result in kdiv is bad. In order to solve the problem i should probably change the .dvi viewer to xdvi? Has someone maybe an idea of how to change the default viewer in kile to xdvi or what could cause the problems in kdvi? Thanks in advance
Comment 1 Thiago Macieira 2005-07-15 13:15:06 UTC
Can you describe what is wrong with kdvi?
Comment 2 Dragomir Deltchev 2005-07-15 15:28:59 UTC
Well there is always a message: 

File corruption! KDVI had trouble interpreting your DVI file. Most likely this means that the DVI file is broken.

And if you click on Details:
The DVI code set a character of an unknown font.
Comment 3 Wilfried Huss 2005-07-17 19:34:34 UTC

*** This bug has been marked as a duplicate of 107796 ***
Comment 4 Stefan Kebekus 2005-07-18 03:47:52 UTC
On Friday 15 July 2005 15:29, Dragomir Deltchev wrote:
[bugs.kde.org quoted mail]
this means that the DVI file is broken.
> 
> And if you click on Details:
> The DVI code set a character of an unknown font.


Hi there,

I assume that you are using RedHat Fedora. The issue is then a known problem 
with a buggy compiler that RedHat uses. The compiler has a number of bugs, 
and is explicitly blacklisted as not suitable for compiling KDE. 

The upcoming KDE 3.4.2 release will contain a workaround that solves this 
particular issue. It is to be expected, however, that other problems will 
come up as long as RedHat keeps using compilers with known issues.

Best,

Stefan.