[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#794420: marked as done (ghostscript: ps2pdf13 produces incomplete files with PS files generated by Windows printer drivers)

Your message dated Fri, 05 Jan 2024 23:11:22 -0600
with message-id <10402422.nUPlyArG6x@riemann>
and subject line Re: Test file
has caused the Debian Bug report #794420,
regarding ghostscript: ps2pdf13 produces incomplete files with PS files generated by Windows printer drivers
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 owner@bugs.debian.org
immediately.)


-- 
794420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794420
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ghostscript
Version: 9.06~dfsg-2+deb8u1
Severity: important

When setting up a Windows client to print through my main Debian box, I noticed
that the test page came out incomplete - only the logo and one letter was
printed.

I tracked this down to CUPS using compatibility version 1.3 when converting the
PS file to a PDF file (/usr/lib/cups/filters/pstopdf). This can be reproduced
using ps2pdf13 and ps2pdf12 with the file I indent to attach to this bug report
(hoping that I can attach files).

I've changed the CUPS filter to use PDF compatibility version 1.2 and can now
print from Windows - this might be an acceptable workaround until the underlying
cause has been fixed but this is, of course, a different package. I'm still
submitting this bug to ghostscript because this is where I believe it's
ultimately located.

The importance of this defect is, I believe, relatively high because it appears
toprevent any Windows client from printing anything on a Debian 8.1 server, at
least in situations as mine whether the printer doesn't speak Postscript and
CUPS needs to handle the input file.

Please stand by for the example file (the printer test page from Windows).

-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (700, 'stable'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.7-ckt11-amd64-cm1.5 (SMP w/6 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ghostscript depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  gsfonts                1:8.11+urwcyr1.0.7~pre44-4.2
ii  libc6                  2.19-18
ii  libgs9                 9.06~dfsg-2+deb8u1

ghostscript recommends no packages.

Versions of packages ghostscript suggests:
ii  ghostscript-x  9.06~dfsg-2+deb8u1

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Mon, 03 Aug 2015 09:20:56 +0200 Christian Mueller <chris@mumac.de> wrote:
> I tried to send the test file as base64-encoded email yesterday (71KB, 
> around 16 A4 pages when printed) but it never showed up in the bug 
> report; I guess it might have been too large. Do you have any other 
> means to upload test files?

This bug is not actionable without an example file.  Given that it is now 8 
years old, I'm just closing it.  Please re-open with an example file if issue 
remains.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: