GNOME Bugzilla – Bug 701576
Evince doesn't respect pritable area
Last modified: 2018-05-22 15:07:14 UTC
If i print a PDF (with setting "Fit to Printable Area" or "Shrink to Printable Area", doesn't matter), some part of the document is missing at the right side. I expect the document to be shrunken so that it is fully visible. I already tried to alter ImageableArea in my printer's ppd according to the following link, but that doesn't help. http://forums.gentoo.org/viewtopic-t-573815-start-0.html moi@moi-Latitude-E6520:~$ lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 moi@moi-Latitude-E6520:~$ apt-cache policy evince evince: Installiert: 3.6.1-1ubuntu3 Installationskandidat: 3.6.1-1ubuntu3 Versionstabelle: *** 3.6.1-1ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status Printer is Brother HL2240.
How can I help to fix the problem?
Is "Autorotate and Center" selected? If not, is there any change? Can you reproduce the issue if you print to a PDF file under the same conditions?
Yes, "Autorotate and Center" is selected. What would be the issue if I print to a PDF file, which should be printable everywhere? It is *not* the problem that evince somehow crops the output, but that my printer isn't able to print right until the border of the sheet. Evince should respect that limitation and should shrink the page to the size of the area printable by my printer.
(In reply to comment #3) > Yes, "Autorotate and Center" is selected. > > What would be the issue if I print to a PDF file, which should be printable > everywhere? It is *not* the problem that evince somehow crops the output, but > that my printer isn't able to print right until the border of the sheet. I am trying to narrow the issue and trying to understand it better. I can not reproduce the issue, but if you could reproduce by printing to a file, then I could spend more time trying to replicate it or identify other duplicate files. For what it is worth, there has been other bugs that can be replicated by printing to a file. Replicate the issue is an important part to prioritize bugs, for doing that, we need the descriptions to be as accurate as possible. For instance, you have not described whether this happens with any document or with one in particular, or which size of the page have the document(s), do they have portrait pages or landscape, and so on. > Evince should respect that limitation and should shrink the page to the size of > the area printable by my printer. The problem could in any part of the stack that evince depends on. You are describing a symptom, and I am asking for more information. If you use 'pdftocairo -ps file.pdf output.ps' and get similar results, then the problem might be in cairo. If you would like to help to fix this bug, you could start by replicating the bug with evince 3.8 (or better master), with poppler 0.22 and a recent cairo. If still you can do it, try to provide more details so we can replicate it as well.
Created attachment 247101 [details] Original
Created attachment 247102 [details] pdftocairo
Created attachment 247103 [details] Print to file
Created attachment 247104 [details] Scan of printer output
I created a test file and attached it and various outputs. Only the print shows the described behavior.
I tried to build evince master (according to https://live.gnome.org/Evince/GettingEvince), but get the following error: checking for LIBDOCUMENT... no configure: error: Package requirements (gtk+-3.0 >= 3.8.0 gio-2.0 >= 2.36.0 gmodule-no-export-2.0 >= 2.36.0 gmodule-2.0) were not met: Requested 'gtk+-3.0 >= 3.8.0' but version of GTK+ is 3.6.4 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables LIBDOCUMENT_CFLAGS and LIBDOCUMENT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. *** Fehler während Phase configure von evince: ########## Fehler beim Ausführen von ./autogen.sh --prefix /home/moi/code/evince/install --libdir '/home/moi/code/evince/install/lib64' --enable-introspection --disable-nautilus --without-keyring *** [3/3] [1] Phase configure erneut ausführen [2] Fehler ignorieren und bei build fortsetzen [3] Bei diesem Modul aufgeben [4] Shell starten [5] Konfiguration neu laden [6] Zu Phase »Ordner säubern und neu starten« gehen [7] Zu Phase »clean« gehen [8] Zu Phase »distclean« gehen Maybe the script should also checkout the required version of GTK.
(In reply to comment #10) > I tried to build evince master (according to > https://live.gnome.org/Evince/GettingEvince), but get the following error: > > checking for LIBDOCUMENT... no > configure: error: Package requirements (gtk+-3.0 >= 3.8.0 gio-2.0 >= 2.36.0 > gmodule-no-export-2.0 >= 2.36.0 gmodule-2.0) were not met: > > Requested 'gtk+-3.0 >= 3.8.0' but version of GTK+ is 3.6.4 > [...] > Maybe the script should also checkout the required version of GTK. Indeed. I updated the script and the instructions there. Please, download again the jhbuildrc-evince file and try again. I would recommend you to use jhbuild from git, which contains the definitions to build everything needed. However, you might need to apply the patch in https://bugzilla.gnome.org/show_bug.cgi?id=702682
I had also to install these packages: gperf ragel libxtst-dev cmake valac flex bison. And then ran into the next error: *** Konfiguration läuft gvfs *** [19/19] ./autogen.sh --prefix /home/moi/code/evince/install --libdir '/home/moi/code/evince/install/lib64' --disable-gtk-doc libtoolize: putting auxiliary files in `.'. libtoolize: linking file `./ltmain.sh' libtoolize: You should add the contents of the following files to `aclocal.m4': libtoolize: `/usr/share/aclocal/libtool.m4' libtoolize: `/usr/share/aclocal/ltoptions.m4' libtoolize: `/usr/share/aclocal/ltversion.m4' libtoolize: `/usr/share/aclocal/ltsugar.m4' libtoolize: `/usr/share/aclocal/lt~obsolete.m4' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:587: warning: macro `AM_PATH_LIBGCRYPT' not found in library configure.ac:20: installing `./compile' configure.ac:17: installing `./config.guess' configure.ac:17: installing `./config.sub' configure.ac:4: installing `./install-sh' configure.ac:4: installing `./missing' client/Makefile.am: installing `./depcomp' daemon/Makefile.am:32: `%'-style pattern rules are a GNU make extension daemon/Makefile.am:39: `%'-style pattern rules are a GNU make extension metadata/Makefile.am:56: `%'-style pattern rules are a GNU make extension configure.ac:587: error: possibly undefined macro: AM_PATH_LIBGCRYPT If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. *** Fehler während Phase configure von gvfs: ########## Fehler beim Ausführen von ./autogen.sh --prefix /home/moi/code/evince/install --libdir '/home/moi/code/evince/install/lib64' --disable-gtk-doc *** [19/19] [1] Phase configure erneut ausführen [2] Fehler ignorieren und bei build fortsetzen [3] Bei diesem Modul aufgeben [4] Shell starten [5] Konfiguration neu laden [6] Zu Phase »Ordner säubern und neu starten« gehen [7] Zu Phase »clean« gehen [8] Zu Phase »distclean« gehen
Because of the error message, it is likely you already have the latest evince. gvfs is just to allow evince to read the metadata in each file (something nice to have, but not required). However, I just updated the custom modulesets. If you try again, it should work. You can also ping me in #evince at irc.gnome.org.
Next error: *** Fehler während Phase checkout von cairo: The requested branch "1.12" is not available. Neither locally, nor remotely in the origin remote. *** [3/20] Thanks for your help.
That branch was removed in a short period of time. It should not be a problem now.
Also, if you have upgraded to 3.10, you probably have a newer Evince. Does it happen there?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/350.