Bug 107796 - kdvi generate File corruption erroe message and does not show correct dvi image
Summary: kdvi generate File corruption erroe message and does not show correct dvi image
Status: CLOSED FIXED
Alias: None
Product: kdvi
Classification: Miscellaneous
Component: general (show other bugs)
Version: 1.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Stefan Kebekus
URL:
Keywords:
: 109129 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-20 17:26 UTC by kiheonyun
Modified: 2005-07-17 19:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
DVI exhibiting the problem (276 bytes, application/octet-stream)
2005-06-25 15:38 UTC, gwh2
Details
2116904.dvi (892 bytes, application/x-dvi)
2005-06-25 19:05 UTC, Jacob Greenstein
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kiheonyun 2005-06-20 17:26:19 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Fedora RPMs
OS:                Linux

I installed Fedora core 4 , kile 1.8.1 and kde 3.4.1 including kdegraphics-3.4.1-1.0.fc4.kde.
I guess tetex generate good dvi file because it can be read by using xdvi and it generates ps and pdf correctly. But kdvi does not show the dvi file correctly and it always generates several error message:

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

Details: 
The DVI code set a character of an unknown font.

Do you know any solution of the problem?
Comment 1 Stefan Hoelldampf 2005-06-21 10:55:18 UTC
The same problem occurs with "old" DVI files created on Fedora Core 3 (tetex-2.0.2-21.3), too.
Comment 2 Jacob Greenstein 2005-06-24 00:37:12 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Jacob Greenstein 2005-06-24 00:40:50 UTC
This behavior does not depend on the origin of the DVI file. The message is produced when the first few pages of the document are viewed.
Comment 4 Stefan Kebekus 2005-06-25 14:58:52 UTC
Hi,

thank you for your bug reports. I believe that this issue could be the same as bug #107065, but I am not certain yet.

Unfortunately, I have not been able to reproduce the issue on any of my machines, and I start to suspect that this could really be a problem with the compilers that RedHat Fedora use. 

To help me track down the issue, could you please try to shorten the DVI file so that is no more than one page, at best no more than a few words, and send me the file.

Best,

Stefan.
Comment 5 gwh2 2005-06-25 15:38:33 UTC
Created attachment 11578 [details]
DVI exhibiting the problem

Every DVI I've tried, no matter how short, generates the error.  Some of them
also place stray characters on the page.  I've attached a short DVI that gives
the error and displays an extraneous infinity sign on Fedora Core 4.
Comment 6 Jacob Greenstein 2005-06-25 19:05:49 UTC
Hi,

Thank you very much.

As a matter of fact, the compiler which Fedora Core 4 uses is blacklisted by 
KDE, but so far the only bug I noticed was this one (the reason might be due 
to the fact that I am using TeX quite a lot).

I am attaching a short DVI file produced on the Fedora Core 4 machine in 
question. The effect, however, is more complicated than I thought: the error 
never appears further than the 2nd or 3rd page, but strange symbols can 
appear anywhere in the document.

Best,
Jacob


Created an attachment (id=11580)
2116904.dvi
Comment 7 Stefan Kebekus 2005-07-04 11:30:40 UTC
Hi,

thank you for your bug report. The issue that you have reported is really a bug in the C++ compiler that RedHat uses for Fedore Core 4. The compiler is known to have issues, and is explicitly blacklisted as unsuitable to compile KDE. I have added a workaround for this particular bug to the KDVI source files, and KDVI seems to run fine now. 

The workaround will be contained in the upcoming KDE 3.4.2 release. It must be expected, however, that the buggy compile will cause more problems, at other places. Thus, I would strongly urge you to complain to the makers of Fedore about the issue.

Best,

Stefan.
Comment 8 Martin Ellis 2005-07-16 21:34:48 UTC
Was the workaround for this "File corruption" bug also applied to trunk?

I am seeing the same error with the Kubuntu 'Breezy' toolchain.
I've removed the packaged kdvi so I'm pretty sure I'm using the
version in trunk.  Or was the workaround not part of kdvi, but
elsewhere?

Thanks
Comment 9 Wilfried Huss 2005-07-17 19:34:38 UTC
*** Bug 109129 has been marked as a duplicate of this bug. ***