Bug 231301 - print/gv: unusable due to distorted non-refresh screen after page change
Summary: print/gv: unusable due to distorted non-refresh screen after page change
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-11 15:07 UTC by O. Hartmann
Modified: 2019-08-18 04:21 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description O. Hartmann 2018-09-11 15:07:46 UTC
Running OS: FreeBSD 12-ALPHA5 (12.0-ALPHA5 #123 r338586: Tue Sep 11 14:41:27 CEST 2018 amd64), ports tree at Revision: 479524, all ports up to date so far including recent ghostscript updates.

Phenomenon: Creating a Postscript document via LaTeX (print/texlive-full, 2015) and trying to display the result via print/gv results in a complete wrecked view on the document when moving from one page to another, either forward or backward. It looks to me like the content of the previous shown page of the PS document is not cleared and the content of the new page is simply printed over the old page. After paging forward and backward a couple of pages, the whole content displayed via gv is not readable any more. A kind of refresh with the expected clearing of the previous page's content can be forced by refitting the page to anything provided by the menu of gv.

The same happens if the document is compiled by LaTeX/pdflatex as PDF and tried to be shown/displayed via gv.

The problem also occurs with commercial PDF's (books), which has been displayed so far without problems via gv - until recently.

I have, so far, recompiled all requisites of print/gv and most parts of the X11 system, but with no success. I also deleted the local config file, ~/.gv, and the global one and left the system with the defaults after reinstallation - without any success. 

I can not say whether this is a FreeBSD ports specific problem or a general bug in print/gv occuring with recent changes to ghostscript.
Comment 1 Walter Schwarzenfeld freebsd_triage 2019-08-11 10:48:19 UTC
Is this still relevant?
Comment 2 O. Hartmann 2019-08-18 04:20:55 UTC
Magically disappeared over time ...