DebuggingEvince
|
Size: 4110
Comment: added link to Italian translation
|
Size: 4275
Comment: Misc. minor presentation fixes
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| [[http://gnome.org/projects/evince/|Evince]] is the default application in Ubuntu for opening .pdf, .ps, .djvu and other similar types of files. | [[http://gnome.org/projects/evince/|Evince]] is the default application in Ubuntu for opening .pdf, .ps, .djvu, and other supported files as outlined by the project. |
| Line 10: | Line 10: |
| Most bugs related to Evince fall into 3 categories: 1. Evince crashes when I open a specific document (or when I open it and perform a specific action, like scroll, zoom or rotate) 1. Evince does not display ("render") the document correctly 1. Evince displays the document as it should, but then doesn't print it correctly |
= Not a bug = |
| Line 15: | Line 12: |
| = Common issues = | The following specific cases are not bugs to report: |
| Line 17: | Line 14: |
| == Dvi files == | == Evince can't display dvi files == |
| Line 19: | Line 16: |
| Evince uses texlive to render .dvi files. If you cannot open a .dvi file (error message "Unable to open document. DVI document has incorrect format"), install the '''texlive''' package and try again. (There's [[https://bugs.launchpad.net/ubuntu/+source/evince/+bug/42410|bug report #42410]] about correcting this error message) | Evince uses texlive to render .dvi files. If you cannot open a .dvi file (error message "Unable to open document. DVI document has incorrect format"), install the '''texlive''' package and try again. (There's [[https://bugs.launchpad.net/ubuntu/+source/evince/+bug/42410|bug report #42410]] about correcting this error message). |
| Line 21: | Line 18: |
| == CJK fonts == | == Evince can't display CJK fonts == |
| Line 27: | Line 24: |
| In all reports, please ensure you attach an uncompressed/untarred document that the issue is reproducible with. |
|
| Line 29: | Line 28: |
| In case Evince crashes, follow standard [[DebuggingProgramCrash]] procedures. | If Evince crashes, please report this following [[https://wiki.ubuntu.com/ReportingBugs]]. |
| Line 33: | Line 32: |
| If the crash/incorrect rendering appears only with a specific document, obtaining that document will help. Here's a stock reply to use in this case: {{{ Thank you for taking the time to report this bug and helping to make Ubuntu even better! It would be quite helpful if you attach the document you are having a problem with so we can better recreate this bug and work on fixing it. Thanks in advance. }}} Once you have the document and have confirmed it doesn't render as it's supposed to in Evince, you have to find the right package for this bug. Evince uses: |
Once you have the document and have confirmed it doesn't render as it's supposed to in Evince, you have to find the correct package for this bug. Evince uses: |
| Line 46: | Line 39: |
| * Adobe Reader (package '''acroread''', available in the [[http://medibuntu.org/|Medibuntu]] repository) * Xpdf (package '''xpdf-reader''') * ePdfView * okular * for .ps files: ghostscript * for .djvu files: djVuLibre (package '''djview4''') |
* PDF * Adobe Reader - package [[https://launchpad.net/ubuntu/+source/acroread|acroread]] in Precise only, or Adobe Reader via the latest [[https://launchpad.net/~ubuntu-wine/+archive/ubuntu/ppa|WINE]]. * Xpdf - package [[https://launchpad.net/ubuntu/+source/xpdf|xpdf]] * Okular - package [[https://launchpad.net/ubuntu/+source/okular|okular]] * ePdfView - package [[https://launchpad.net/ubuntu/+source/epdfview|epdfview]] in Precise only * PostScript (.ps) * ghostscript * .djvu * djVuLibre - package [[https://launchpad.net/ubuntu/+source/djview4|djview4]] |
| Line 59: | Line 55: |
| Sometimes, when a document printed from evince doesn't print correctly, it is not a problem with Evince, but with cups, or the specific printer driver. | It is best to file printing problems following [[https://wiki.ubuntu.com/DebuggingPrintingProblems]] first. If it turns out to be a bug in Evince, it may be reassigned. |
| Line 61: | Line 57: |
| = Triage responses = | |
| Line 62: | Line 59: |
| = Other issues = | No document attached: {{{ Thank you for taking the time to report this and helping to make Ubuntu better. Could you please attach an example document that demonstrates this issue? }}} |
| Line 64: | Line 62: |
| == How to Forward == | = Reporting bugs upstream = |
| Line 66: | Line 64: |
| * Upstream Evince bugs are at http://bugzilla.gnome.org/browse.cgi?product=evince * Upstream Poppler bugs are at http://bugs.freedesktop.org/query.cgi |
Once the report has been marked Triaged, then one would want to next gather the required information necessary to forward to the appropriate upstream tracker. This includes the version Evince, poppler, and cairo via a terminal: {{{ apt-cache policy evince libcairo2 libpoppler[0-9] }}} As well, if reporting an Evince crash, one may post the backtrace as a comment, and bugzilla will wrap it up into a button to expand out. * Evince: [[http://bugzilla.gnome.org/browse.cgi?product=evince]] * Poppler: [[http://bugs.freedesktop.org/query.cgi]] |
| Line 69: | Line 70: |
| == Backporting Fixes == | = Backporting Fixes = |
| Line 71: | Line 72: |
| Bug fixes are normally backported to all supported Ubuntu releases (you can see which releases are still supported [[http://en.wikipedia.org/wiki/List_of_Ubuntu_releases#Release_history|here]]). | Bug fixes are reviewed for backporting to all [[https://wiki.ubuntu.com/Releases|supported Ubuntu releases]] following [[https://wiki.ubuntu.com/StableReleaseUpdates]]. |
| Line 73: | Line 74: |
| However, this is not always possible, for example when the code architecture has changed significantly. This means that sometimes bugs are marked as "Fix Released" even when they have been fixed only in recent versions of evince/poppler/etc. |
Available languages : Italiano,
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Introduction
Evince is the default application in Ubuntu for opening .pdf, .ps, .djvu, and other supported files as outlined by the project.
Not a bug
The following specific cases are not bugs to report:
Evince can't display dvi files
Evince uses texlive to render .dvi files. If you cannot open a .dvi file (error message "Unable to open document. DVI document has incorrect format"), install the texlive package and try again. (There's bug report #42410 about correcting this error message).
Evince can't display CJK fonts
CJK stands for Chinese-Japanese-Korean. A pdf that includes such text but lacks the embedded fonts will not render correctly unless you install the package poppler-data.
Debugging procedure
In all reports, please ensure you attach an uncompressed/untarred document that the issue is reproducible with.
Crash or Freeze
If Evince crashes, please report this following https://wiki.ubuntu.com/ReportingBugs.
Rendering issues
Once you have the document and have confirmed it doesn't render as it's supposed to in Evince, you have to find the correct package for this bug. Evince uses:
libpoppler for rendering pdf files
libspectre for rendering postscript files
libpango, libfreetype and fontconfig for fonts choosing and rendering
libcairo for 2D vector graphics
Try opening it with different viewers to try and isolate the problem:
PostScript (.ps)
- ghostscript
- .djvu
djVuLibre - package djview4
When pdf files don't include the embedded fonts used in the document, then if Ubuntu doesn't have the specific font installed, it will search for the nearest equivalent, using fc-match <font>.
It might also be helpful to use the pdfinfo and pdffonts utils (included in the poppler-utils package).
Printing problems
It is best to file printing problems following https://wiki.ubuntu.com/DebuggingPrintingProblems first. If it turns out to be a bug in Evince, it may be reassigned.
Triage responses
No document attached:
Thank you for taking the time to report this and helping to make Ubuntu better. Could you please attach an example document that demonstrates this issue?
Reporting bugs upstream
Once the report has been marked Triaged, then one would want to next gather the required information necessary to forward to the appropriate upstream tracker. This includes the version Evince, poppler, and cairo via a terminal:
apt-cache policy evince libcairo2 libpoppler[0-9]
As well, if reporting an Evince crash, one may post the backtrace as a comment, and bugzilla will wrap it up into a button to expand out.
Backporting Fixes
Bug fixes are reviewed for backporting to all supported Ubuntu releases following https://wiki.ubuntu.com/StableReleaseUpdates.
DebuggingEvince (last edited 2014-12-29 01:44:55 by penalvch)