Your message dated Mon, 26 Jun 2017 17:00:39 +0000
with message-id
<CALiO0=GQauQCRWqXt0teBtSod7=kvgcgdrxvwpysst2n6xp...@mail.gmail.com>
and subject line Re: Bug#866007: further info
has caused the Debian Bug report #866007,
regarding gimp: printing halts at step: rendering completed
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.)
--
866007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866007
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gimp
Version: 2.8.18-1
Severity: important
Dear Gimp Debian maintainer,
when printing from Gimp, I cannot obtain my hardcopy, printing halts
at the step: rendering completed, as reported in localhost:631 printer status.
Printing works correctly in all other applications I tried, e.g. okular.
Until I cancel the job, cups keeps spamming the logs, apparently trying to solve
the problem.
I think the problem may be linked to the following log excerpt:
------------------------------------------------
D [26/Jun/2017:15:06:36 +0200] [Notifier] state=3
D [26/Jun/2017:15:06:36 +0200] [Notifier] JobProgress
D [26/Jun/2017:15:06:36 +0200] [Notifier] state=3
D [26/Jun/2017:15:06:36 +0200] [Notifier] PrinterStateChanged
D [26/Jun/2017:15:06:36 +0200] [Job 17] Unrecoverable error: rangecheck in
setpagedevice
D [26/Jun/2017:15:06:36 +0200] [Job 17] Operand stack:
D [26/Jun/2017:15:06:36 +0200] [Job 17] true true --nostringval--
--nostringval-- --nostringval-- --nostringval-- --nostringval--
--nostringval-- --nostringval-- --nostringval-- tru
e --nostringval-- %MediaSource 0 %MediaDestination 0 .LockSafetyParams
true --nostringval-- --nostringval-- --nostringval-- 7 --nostringval--
false --nostringval--
D [26/Jun/2017:15:06:36 +0200] [Job 17] Rendering completed
D [26/Jun/2017:15:06:36 +0200] cupsdMarkDirty(---J-)
------------------------------------------------
Best regards
Fulvio Ciriaco
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gimp depends on:
ii gimp-data 2.8.18-1
ii libaa1 1.4p5-44+b1
ii libatk1.0-0 2.22.0-1
ii libbabl-0.1-0 0.1.18-1
ii libbz2-1.0 1.0.6-8.1
ii libc6 2.24-11
ii libcairo2 1.14.8-1
ii libdbus-1-3 1.10.18-1
ii libdbus-glib-1-2 0.108-2
ii libexif12 0.6.21-2+b2
ii libexpat1 2.2.0-2
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.2
ii libgdk-pixbuf2.0-0 2.36.5-2
ii libgegl-0.3-0 0.3.8-4
ii libgimp2.0 2.8.18-1
ii libglib2.0-0 2.50.3-2
ii libgs9 9.20~dfsg-3.2
ii libgtk2.0-0 2.24.31-2
ii libgudev-1.0-0 230-3
ii libice6 2:1.0.9-2
ii libjpeg62-turbo 1:1.5.1-2
ii libjson-glib-1.0-0 1.2.6-1
ii liblcms2-2 2.8-4
ii libmng1 1.0.10+dfsg-3.1+b5
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii libpangoft2-1.0-0 1.40.5-1
ii libpng16-16 1.6.28-1
ii libpoppler-glib8 0.48.0-2
ii librsvg2-2 2.40.16-1+b1
ii libsm6 2:1.2.2-1+b3
ii libtiff5 4.0.8-2
ii libwmf0.2-7 0.2.8.4-10.6
ii libx11-6 2:1.6.4-3
ii libxcursor1 1:1.1.14-1+b4
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxmu6 2:1.1.2-2
ii libxpm4 1:3.5.12-1
ii libxt6 1:1.1.5-1
ii python 2.7.13-2
ii python-gtk2 2.24.0-5.1
ii python2.7 2.7.13-2
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages gimp recommends:
ii ghostscript 9.20~dfsg-3.2
Versions of packages gimp suggests:
ii gimp-data-extras 1:2.0.2-1
ii gimp-help-en [gimp-help] 2.8.2-0.1
ii gvfs-backends 1.30.4-1
ii libasound2 1.1.3-5
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Jun 26, 2017, 10:51 AM fulvio ciriaco <[email protected]> wrote:
> Dear Maintainer,
> apparently the bug is triggered by setting (unknowingly, sorry, in my
> case) an unsupported paper size.
> Please close the ticket.
>
> Fulvio Ciriaco
>
--- End Message ---
