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

Bug#847462: marked as done (printer-driver-cups-pdf: make very ugly and uselss pdf which are not searchables)

Your message dated Mon, 27 Sep 2021 15:57:50 +0300
with message-id <CAPZXPQfkcdC-=rNczTh2vCwpf_K+X5407N1=oNY-dTGRKphR3g@mail.gmail.com>
and subject line Re: Bug#425405: Not a bug
has caused the Debian Bug report #425405,
regarding printer-driver-cups-pdf: make very ugly and uselss pdf which are not searchables
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.)


-- 
425405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425405
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: printer-driver-cups-pdf
Severity: grave
Justification: renders package unusable

Dear Maintainer,

It's not possible to make usable pdf, I have triyed to use the unstable version off the package and the result is the same



-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=ca_ES.utf8, LC_CTYPE=ca_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Btw, I notice that this bug was filed ages ago against CUPS-PDF
2.4.2-3 which dates back from 2007.

The oldest supported release (oldoldstable) has 2.6.1-22 which dates
back from 2016.

All newer Debian releases ship with some 3.0.1 package.

I am thus closing this bug. Feel free to re-open it if the issue still
applies to current packages.

Martin-Éric

ma 27. syysk. 2021 klo 14.26 Martin-Éric Racine
(martin-eric.racine@iki.fi) kirjoitti:
>
> Does this issue still apply to what currently is in Bullseye?
>
> Martin-Éric
>
> pe 4. kesäk. 2021 klo 10.30 Jonas Smedegaard (jonas@jones.dk) kirjoitti:
> >
> > Hi Jonathan,
> >
> > Quoting Jonathan Nieder (2021-06-04 04:27:16)
> > > Jonas Smedegaard wrote:
> > > > I agree that this is unlikely a bug in Ghostscript.
> > > >
> > > > The test PDF provided by Jonathan Nieder _is_ searchable with Evince
> > > > 3.38.2-1.
> > > >
> > > > If same file was not searchable with Evince available in January
> > > > 2011, then the issue might be the encoding of the strings in the
> > > > PDF, or it might be something else that confused that older release
> > > > of Evince.
> > > >
> > > > But that test file was produced by LibreOffice.  I would expect that
> > > > a file generated by cups-pdf would instead have cups-pdf as creator
> > > > in the metadata.
> > > >
> > > > I therefore suspect that the test PDF file should be ignored for
> > > > this issue, and that the originally reported issue is a different
> > > > one:
> > > [...]
> > > > For the record: If you suspect that an issue is in Ghostscript then
> > > > please provide the ghostscript command that causes this issue -
> > > > without that the only possible action is to tag it as unreproducible
> > > > and close it, which is not really helpful.
> > >
> > > This response is puzzling.  The example that I produced was a simple
> > > postscript file and then a ps2pdf command that invokes ghostscript to
> > > produce this issue.  I don't understand why you're insisting
> > > simultaneously that I should have
> > >
> > > - used cups-pdf instead of using ghostscript directly
> > > - used ghostscript directly instead of using a larger pipeline that
> > >   invokes it
> > >
> > > since I don't see how those are possible to do at the same time.
> >
> > That last paragraph above was targeted others than you, Jonathan, and I
> > agree: _Either_ investigate as cups-pdf issue _or_ as ghostscript issue.
> >
> > Let me try clarify by rephrasing the sentence I suspect caused
> > confusion:
> >
> > If anyone still suspect that an issue is in Ghostscript then please
> > provide the ghostscript command that causes it, like Jonathan did.
> >
> > Sorry for my ambiguity, and thanks for pointing it out,
> >
> >
> >  - Jonas
> >
> > --
> >  * Jonas Smedegaard - idealist & Internet-arkitekt
> >  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
> >
> >  [x] quote me freely  [ ] ask before reusing  [ ] keep private

--- End Message ---
Reply to: