Your message dated Fri, 28 Apr 2017 08:10:49 -0300
with message-id
<caafdzj8grjh8tpm+4okzsfgap6ztteerg9tbk9xu9bjiiv8...@mail.gmail.com>
and subject line Re: Bug#551557: Acknowledgement (evince: Takes an insane
amount of time and CPU to print)
has caused the Debian Bug report #551557,
regarding evince: Takes an insane amount of time and CPU to print
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
551557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551557
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: evince
Version: 2.28.0-2
Severity: normal
When printing some PDF files in 2 pages per sheet, the print takes an
insane amount of time to occur. The first sheet will come out, wait a
few minutes, the second sheet comes out, etc.
There is a gs process doing a lot of work during this time. That process
is run by user lp, so I'm guessing this is not really a bug in evince,
but since okular prints the same pdf without taking so much time and
CPU, there must be a difference between okular and evince printing-wise,
and maybe you can tell where the real bug is (and reassign
appropriately).
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages evince depends on:
ii evince-common 2.28.0-2 Document (postscript, pdf) viewer
ii gconf2 2.28.0-1 GNOME configuration database syste
ii gnome-icon-theme 2.28.0-1 GNOME Desktop icon theme
ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit
ii libc6 2.9-27 GNU C Library: Shared libraries
ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst
ii libdbus-glib-1-2 0.82-2 simple interprocess messaging syst
ii libevince1 2.28.0-2 Document (postscript, pdf) renderi
ii libfontconfig1 2.6.0-4 generic font configuration library
ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib
ii libgconf2-4 2.28.0-1 GNOME configuration database syste
ii libglib2.0-0 2.22.2-2 The GLib library of C routines
ii libgnome-keyring0 2.26.1-1 GNOME keyring services library
ii libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface
ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library
ii libnautilus-extension1 2.28.0-2 libraries for nautilus components
ii libpango1.0-0 1.26.0-1 Layout and rendering of internatio
ii libpoppler-glib4 0.12.0-2 PDF rendering library (GLib-based
ii libsm6 2:1.1.1-1 X11 Session Management library
ii libx11-6 2:1.2.2-1 X11 client-side library
ii libxml2 2.7.6.dfsg-1 GNOME XML library
ii shared-mime-info 0.70-1 FreeDesktop.org shared MIME databa
ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime
Versions of packages evince recommends:
ii dbus-x11 1.2.16-2 simple interprocess messaging syst
ii gvfs 1.4.0-3 userspace virtual filesystem - ser
Versions of packages evince suggests:
ii nautilus 2.28.0-2 file manager and graphical shell f
pn poppler-data <none> (no description available)
ii unrar 1:3.9.6-1 Unarchiver for .rar files (non-fre
-- no debconf information
--- End Message ---
--- Begin Message ---
On Apr 28, 2017 08:07, "Brian Potkin" <[email protected]> wrote:
On Mon 19 Oct 2009 at 00:21:38 -0300, Felipe Sateler wrote:
> Hmm, changing the printer driver (and PPD, I guess) to the HPLIP one
> seems to resolve the issue. I suppose this means that the real bug is in
> the other driver. I forgot to mention earlier that my printer is an HP
> LaserJet 1010. I'm still leaving the bug assigned to evince because for
> some reason okular avoids this issue while evince doesn't (and I can't
> find where the original PPD came from :/).
There have been signifiant changes to the printing system in the past
nine years, sufficient to make any debugging of this issue very, very
difficult and time-intensive. Files from Evince and Okular probably took
different routes through the filtering system of the time. They
certainly take different routes today (Evince sends a PDF, Okular sends
PostScript). Not having the original PPD makes it impossible to
undertake any serious investigation.
I would recommend this report be closed.
Agreed. This issue has long become non-actionable. Thus I'm closing it.
Saludos
--- End Message ---
