Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 162439 - [patch] kdvi cannot correctly display dvi-files due to a compiler error
[patch] kdvi cannot correctly display dvi-files due to a compiler error
Status: CLOSED DUPLICATE of bug 162430
Product: Fedora
Classification: Fedora
Component: kdegraphics (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
: Patch
Depends On:
  Show dependency treegraph
Reported: 2005-07-04 14:11 EDT by Stefan Hoelldampf
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-04 15:01:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
upstream patch (809 bytes, patch)
2005-07-04 14:16 EDT, Stefan Hoelldampf
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
KDE Software Compilation 107065 None None None Never
KDE Software Compilation 107796 None None None Never

  None (edit)
Description Stefan Hoelldampf 2005-07-04 14:11:44 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
kdvi cannot correctly display dvi-files due to a compiler error. An error message like "The DVI code set a character of an unknown font." appears and the output is wrong.

An upstream workaround has already been committed to the upcoming KDE 3.4.2 branch.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open a dvi-file with kdvi.

Actual Results:  An error messages due to font problems appears.

Expected Results:  No error.

Additional info:
Comment 2 Ngo Than 2005-07-04 15:01:11 EDT

*** This bug has been marked as a duplicate of 162430 ***

Note You need to log in before you can comment on or make changes to this bug.