Debian Bug report logs - #670055
cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Cc: Fabian Greffrath <fabian@greffrath.com>

Subject: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Sun, 22 Apr 2012 17:16:51 +0100

[Message part 1 (text/plain, inline)]

Package: cups-filters
Version: 1.0.16-2
Severity: important


The cups package was removed and cups-filters purged. The fonts-liberation package
was installed as the only TrueType font on the system. cups was re-installed.

From comment #55 in bug report #662660 I'd expect a text file to be printed with
the mono-spaced Liberation font. Using a backend similar to the one described in
the cups-filters README the output file in /tmp was empty and the error_log (which
is attached) reported "No usable font available". Adding the ttf-dejavu-core package
restores the capability to print text files.

Regards,

Brian.



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cups-filters depends on:
ii  fonts-liberation  1.07.2-2
ii  ghostscript       9.05~dfsg-4
ii  libc6             2.13-30
ii  libcups2          1.5.2-10
ii  libcupsfilters1   1.0.16-2
ii  libcupsimage2     1.5.2-10
ii  libfontconfig1    2.8.0-3.1
ii  libgcc1           1:4.7.0-3
ii  libijs-0.35       0.35-8
ii  liblcms2-2        2.2+git20110628-2.1
ii  libpoppler13      0.16.7-3
ii  libstdc++6        4.7.0-3
ii  zlib1g            1:1.2.6.dfsg-2

Versions of packages cups-filters recommends:
ii  colord            <none>
ii  foomatic-filters  4.0.15-1
ii  ghostscript-cups  9.05~dfsg-4

Versions of packages cups-filters suggests:
ii  foomatic-db  20120322-1

-- no debconf information

[error_log (text/plain, attachment)]

Message #10 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>

Cc: 670055@bugs.debian.org

Subject: Re: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 23 Apr 2012 07:59:03 +0200

Am Sonntag, den 22.04.2012, 17:16 +0100 schrieb Brian Potkin:
> From comment #55 in bug report #662660 I'd expect a text file to be printed with
> the mono-spaced Liberation font. Using a backend similar to the one described in
> the cups-filters README the output file in /tmp was empty and the error_log (which
> is attached) reported "No usable font available". Adding the ttf-dejavu-core package
> restores the capability to print text files.

Indeed, it is expected to print the page with LiberationSans. I assume
that we are talking about regular text here, with no "special" or e.g.
Chinese glyphs?

What does "fc-match -s FreeMono" give on your system?

 - Fabian

Message #15 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremon102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 23 Apr 2012 09:45:09 +0100

On Mon 23 Apr 2012 at 07:59:03 +0200, Fabian Greffrath wrote:

> Indeed, it is expected to print the page with LiberationSans. I assume
> that we are talking about regular text here, with no "special" or e.g.
> Chinese glyphs?

No, nothing out of the ordinary. Bash scripts, mail from Mutt etc.

> What does "fc-match -s FreeMono" give on your system?

   brian@dektop3:~$ fc-match -s FreeMono
   n022003l.pfb: "Nimbus Mono L" "Regular"
   LiberationMono-Regular.ttf: "Liberation Mono" "Regular"
   LiberationSans-Regular.ttf: "Liberation Sans" "Regular"
   LiberationSerif-Regular.ttf: "Liberation Serif" "Regular"
   d050000l.pfb: "Dingbats" "Regular"
   s050000l.pfb: "Standard Symbols L" "Regular"
   LiberationSansNarrow-Regular.ttf: "Liberation Sans Narrow" "Regular"

n022003l.pfb is from gsfonts.

Cheers,

Brian.

Message #20 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremon102@gmail.com>

Cc: 670055@bugs.debian.org

Subject: Re: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 23 Apr 2012 14:14:15 +0200

Am 23.04.2012 10:45, schrieb Brian Potkin:
>     brian@dektop3:~$ fc-match -s FreeMono
>     n022003l.pfb: "Nimbus Mono L" "Regular"
>     LiberationMono-Regular.ttf: "Liberation Mono" "Regular"

Well, there it is. Strange...

>     [...]
>
> n022003l.pfb is from gsfonts.

Sure, but this is skipped anyway.

I'd like to reproduce this issue. What exactly are you refering to 
when you write "Using a backend similar to the one described in
the cups-filters README ..."?

 - Fabian

Message #25 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: claremont102@gmail.com

Cc: 670055@bugs.debian.org, control <control@bugs.debian.org>

Subject: Re: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Wed, 25 Apr 2012 09:23:50 +0200

tags 670055 moreinfo unreproducible
thanks

I still fail to reproduce this. Quite the contrary, I just printed a 
page with only fonts-liberation and gsfonts-x11 installed; it was 
"Print to File" from gedit, though, but it still worked fine.

I can imagine two different reasons for the failure on your system: 
Either you still have a local copy of the liberation fonts installed 
somewhere, e.g. in ~/.fonts or /usr/local/, and this copy still 
contains the bug that made Liberation-Mono appear non-monospaced 
(#567806). Or your fontconfig is confused or doesn't know about the 
right directory in which the fonts are installed. Could you please try 
to "rm -rf ~/.fontconfig" and run "fc-cache -s -v" as root?

 - Fabian

Message #32 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Thu, 26 Apr 2012 10:53:40 +0100

On Wed 25 Apr 2012 at 09:23:50 +0200, Fabian Greffrath wrote:

> I still fail to reproduce this. Quite the contrary, I just printed a  
> page with only fonts-liberation and gsfonts-x11 installed; it was "Print 
> to File" from gedit, though, but it still worked fine.

"Print to File" doesn't use cups. It produces a pdf file with embedded
fonts dictated by the application.

> I can imagine two different reasons for the failure on your system:  
> Either you still have a local copy of the liberation fonts installed  
> somewhere, e.g. in ~/.fonts or /usr/local/, and this copy still contains 
> the bug that made Liberation-Mono appear non-monospaced (#567806). Or 
> your fontconfig is confused or doesn't know about the right directory in 
> which the fonts are installed. Could you please try to "rm -rf 
> ~/.fontconfig" and run "fc-cache -s -v" as root?

1. I have now installed Squeeze (base system only) on a spare partition
   of another machine and upgraded it to unstable. fonts-liberation and
   gsfonts-x11 were installed first to satisfy the font dependencies of
   cups-filters and fontconfig-config, followed by cups and all its
   Recommends:.

2. Walking in the footsteps of the cups-filters README:

     cupsctl FileDevice=yes; cupsctl LogLevel=debug

     lpadmin -p test -E -v file:/tmp/printout -P /usr/share/ppd/cupsfilters/Generic-PDF_Printer-PDF.ppd

   The file in /tmp/printout is the one to be sent to the printer.

     lp -d test .bashrc

   The result is the same as I described in my first post - an output
   file which is empty. Substituting the Generic-PostScript PPD file
   from foomatic for the Generic-PDF one (first deleting the test print
   queue) makes no difference.
   
3. fontconfig installed. No change to the previous outcome. Moved
   ~/.fontconfig out of the way and did 'fc-cache -s -vfc-cache -s -v'
   as root.

   /usr/share/fonts: skipping, existing cache is valid: 0 fonts, 4 dirs
   /usr/share/fonts/X11: skipping, existing cache is valid: 0 fonts, 3 dirs
   /usr/share/fonts/X11/Type1: skipping, existing cache is valid: 35 fonts, 0 dirs
   /usr/share/fonts/X11/encodings: skipping, existing cache is valid: 0 fonts, 1 dirs
   /usr/share/fonts/X11/encodings/large: skipping, existing cache is valid: 0 fonts, 0 dirs
   /usr/share/fonts/X11/util: skipping, existing cache is valid: 0 fonts, 0 dirs
   /usr/share/fonts/cmap: skipping, existing cache is valid: 0 fonts, 1 dirs
   /usr/share/fonts/cmap/gs-cjk-resource: skipping, existing cache is valid: 0 fonts, 0 dirs
   /usr/share/fonts/truetype: skipping, existing cache is valid: 0 fonts, 1 dirs
   /usr/share/fonts/truetype/liberation: skipping, existing cache is valid: 16 fonts, 0 dirs
   /usr/share/fonts/type1: skipping, existing cache is valid: 0 fonts, 1 dirs
   /usr/share/fonts/type1/gsfonts: skipping, existing cache is valid: 35 fonts, 0 dirs
   /usr/X11R6/lib/X11/fonts: skipping, no such directory
   /usr/local/share/fonts: skipping, existing cache is valid: 0 fonts, 0 dirs
   /var/cache/fontconfig: cleaning cache directory
   fc-cache: succeeded

Apologies for the delay in replying but testing a few times took a little
while. My understanding of font behaviour is rudimentary so I'm not very
sure what is going on here. Please let me know if there is anything else
I can do to help.

Regards,

Brian.

Message #37 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>, 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Thu, 26 Apr 2012 13:23:12 +0200

[Message part 1 (text/plain, inline)]

Am 26.04.2012 11:53, schrieb Brian Potkin:
> "Print to File" doesn't use cups. It produces a pdf file with embedded
> fonts dictated by the application.

Oh, interesting, I didn't even know.

>     The result is the same as I described in my first post - an output
>     file which is empty. Substituting the Generic-PostScript PPD file
>     from foomatic for the Generic-PDF one (first deleting the test print
>     queue) makes no difference.

I have reproduced your steps and... ended up with an actual file in 
/tmp/printout which has the LiberationMono font embedded:

$ ls -l /tmp/printout
-rw------- 1 root root 49741 Apr 26 13:02 /tmp/printout

$ sudo pdffonts /tmp/printout
name                        type              emb sub uni object ID
--------------------------- ----------------- --- --- --- ---------
MGMUUY+LiberationMono       CID TrueType      yes yes no       8  0

> Apologies for the delay in replying but testing a few times took a little
> while. My understanding of font behaviour is rudimentary so I'm not very
> sure what is going on here. Please let me know if there is anything else
> I can do to help.

Could you please get the sources for cups-filters ("sudo apt-get 
build-dep cups-filters; apt-get source cups-filters"), apply the 
attached patch ("quilt import /path/to/patch; quilt push") , rebuild 
the package ("debuild -us -uc") and then install the resulting 
cups-filters package ("sudo dpkg -i ../cups-filters_1.0.16-2_i386.deb")?

Then please try again and tell us the lines in /var/log/cups/error_log 
that contain "###".

 - Fabian

[texttopdf-debug.patch (text/x-diff, attachment)]

Message #42 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Thu, 26 Apr 2012 13:47:39 +0100

On Thu 26 Apr 2012 at 13:23:12 +0200, Fabian Greffrath wrote:

> I have reproduced your steps and... ended up with an actual file in  
> /tmp/printout which has the LiberationMono font embedded:

It's at times like this I begin to wonder what I have failed to do
correctly. :)

> Could you please get the sources for cups-filters ("sudo apt-get  
> build-dep cups-filters; apt-get source cups-filters"), apply the  
> attached patch ("quilt import /path/to/patch; quilt push") , rebuild the 
> package ("debuild -us -uc") and then install the resulting cups-filters 
> package ("sudo dpkg -i ../cups-filters_1.0.16-2_i386.deb")?
>
> Then please try again and tell us the lines in /var/log/cups/error_log  
> that contain "###".

Not something I usually do, but your instructions helped considerably.
Thanks.

Here is the relevant extract from the error_log:

I [26/Apr/2012:13:33:06 +0100] [Job 13] Started filter /usr/lib/cups/filter/texttopdf (PID 14041)
I [26/Apr/2012:13:33:06 +0100] [Job 13] Started filter /usr/lib/cups/filter/pdftopdf (PID 14042)
D [26/Apr/2012:13:33:06 +0100] Discarding unused job-state-changed event...
D [26/Apr/2012:13:33:06 +0100] Returning IPP successful-ok for Send-Document (ipp://localhost:631/printers/test) from localhost
D [26/Apr/2012:13:33:06 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Active clients and dirty files"
D [26/Apr/2012:13:33:06 +0100] cupsdReadClient: 16 WAITING Closing on EOF
D [26/Apr/2012:13:33:06 +0100] cupsdCloseClient: 16
D [26/Apr/2012:13:33:06 +0100] cupsdSetBusyState: newbusy="Printing jobs and dirty files", busy="Printing jobs and dirty files"
D [26/Apr/2012:13:33:06 +0100] [Job 13] Page = 612x792; 18,36 to 594,756
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/n022024l.pfb:Type 1:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/n022003l.pfb:Type 1:100
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf:TrueType:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSerif-Regular.ttf:TrueType:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/d050000l.pfb:Type 1:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/s050000l.pfb:Type 1:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSansNarrow-Regular.ttf:TrueType:
D [26/Apr/2012:13:33:06 +0100] [Job 13] No viable font found
W [26/Apr/2012:13:33:06 +0100] [Job 13] Ignored bad font "FreeMono"
D [26/Apr/2012:13:33:06 +0100] [Job 13] Set job-printer-state-message to "Ignored bad font "FreeMono"", current level=WARN
D [26/Apr/2012:13:33:06 +0100] Discarding unused job-progress event...
D [26/Apr/2012:13:33:06 +0100] Discarding unused printer-state-changed event...
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/n022024l.pfb:Type 1:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/n022003l.pfb:Type 1:100
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf:TrueType:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSerif-Regular.ttf:TrueType:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/d050000l.pfb:Type 1:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/s050000l.pfb:Type 1:
D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSansNarrow-Regular.ttf:TrueType:
D [26/Apr/2012:13:33:06 +0100] [Job 13] No viable font found
W [26/Apr/2012:13:33:06 +0100] [Job 13] Ignored bad font "FreeMono"
E [26/Apr/2012:13:33:06 +0100] [Job 13] No usable font available
D [26/Apr/2012:13:33:06 +0100] [Job 13] Set job-printer-state-message to "No usable font available", current level=ERROR

Message #47 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>, 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Thu, 26 Apr 2012 15:36:54 +0200

Am 26.04.2012 14:47, schrieb Brian Potkin:
> D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/n022024l.pfb:Type 1:
> D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/n022003l.pfb:Type 1:100
> D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf:TrueType:
> D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSerif-Regular.ttf:TrueType:
> D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/d050000l.pfb:Type 1:
> D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/X11/Type1/s050000l.pfb:Type 1:
> D [26/Apr/2012:13:33:06 +0100] [Job 13] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationSansNarrow-Regular.ttf:TrueType:

It's unbelievable! Where the heck is LiberationMono in this list?

I know it's getting absurd, but could you please run "ls -l 
/usr/share/fonts/truetype/liberation" just to make sure that the font 
files are actually installed where they are expected?

Could you please again run "fc-match -s FreeMono" and also "fc-match 
-a FreeMono" to see if there are any differences in the first few 
lines? What does "fc-match FreeMono", i.e. without any additional 
parameters, give?

Do you have some custom fontconfig rules installed?

 - Fabian

Message #52 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Thu, 26 Apr 2012 16:38:54 +0200

[Message part 1 (text/plain, inline)]

Am 26.04.2012 14:47, schrieb Brian Potkin:
> It's at times like this I begin to wonder what I have failed to do
> correctly. :)

Furthermore, could you please install the libfontconfig1-dev package 
and compile the attached source with "gcc fc-test.c -o fc-test 
-lfontconfig".

It's the relevant part from texttopdf.c copied into a dedicated 
executable. Now please try "./fc-test FreeMono" and tell me the 
results. As this is more or less a re-implementation of "fc-match -s", 
the results should be identical up to the point where a monospaced 
truetype font is found. Can you confirm?

 - Fabian

[fc-test.c (text/plain, attachment)]

Message #57 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Thu, 26 Apr 2012 17:53:52 +0100

[Message part 1 (text/plain, inline)]

On Thu 26 Apr 2012 at 15:36:54 +0200, Fabian Greffrath wrote:

> I know it's getting absurd, but could you please run "ls -l  
> /usr/share/fonts/truetype/liberation" just to make sure that the font  
> files are actually installed where they are expected?

-rw-r--r-- 1 root root 118652 Feb 29 19:32 LiberationMono-BoldItalic.ttf
-rw-r--r-- 1 root root 105616 Feb 29 19:32 LiberationMono-Bold.ttf
-rw-r--r-- 1 root root 124376 Feb 29 19:32 LiberationMono-Italic.ttf
-rw-r--r-- 1 root root 108476 Feb 29 19:32 LiberationMono-Regular.ttf
-rw-r--r-- 1 root root 135404 Feb 29 19:32 LiberationSans-BoldItalic.ttf
-rw-r--r-- 1 root root 137272 Feb 29 19:32 LiberationSans-Bold.ttf
-rw-r--r-- 1 root root 162324 Feb 29 19:32 LiberationSans-Italic.ttf
-rw-r--r-- 1 root root 128852 Feb 29 19:32 LiberationSansNarrow-BoldItalic.ttf
-rw-r--r-- 1 root root 110528 Feb 29 19:32 LiberationSansNarrow-Bold.ttf
-rw-r--r-- 1 root root 132796 Feb 29 19:32 LiberationSansNarrow-Italic.ttf
-rw-r--r-- 1 root root 113320 Feb 29 19:32 LiberationSansNarrow-Regular.ttf
-rw-r--r-- 1 root root 139628 Feb 29 19:32 LiberationSans-Regular.ttf
-rw-r--r-- 1 root root 150692 Feb 29 19:32 LiberationSerif-BoldItalic.ttf
-rw-r--r-- 1 root root 146896 Feb 29 19:32 LiberationSerif-Bold.ttf
-rw-r--r-- 1 root root 144308 Feb 29 19:32 LiberationSerif-Italic.ttf
-rw-r--r-- 1 root root 152280 Feb 29 19:32 LiberationSerif-Regular.ttf

> Could you please again run "fc-match -s FreeMono" and also "fc-match -a 
> FreeMono" to see if there are any differences in the first few lines? 
> What does "fc-match FreeMono", i.e. without any additional parameters, 
> give?

The last command gives

   n019003l.pfb: "Nimbus Sans L" "Regular"

The outputs of the other commands are attached. Anything untoward there?

> Do you have some custom fontconfig rules installed?

The installation I'm working on was put together last night. The basic
packages plus cups. No custom files.

I recollected I have a GNOME install from a live CD. It's barely used and
untouched, apart from updating and a few extra packages. Purging freefont
and dejavu unfortunately gets the same outcome as with the other two
systems.

[The last mail wasn't CC'ed to me]

The result of "./fc-test FreeMono" is:

  C: /usr/share/fonts/X11/Type1/n022024l.pfb
  C: /usr/share/fonts/X11/Type1/n022003l.pfb
  C: /usr/share/fonts/truetype/liberation/LiberationSans-Regular.ttf
  C: /usr/share/fonts/truetype/liberation/LiberationSerif-Regular.ttf
  C: /usr/share/fonts/X11/Type1/d050000l.pfb
  C: /usr/share/fonts/X11/Type1/s050000l.pfb
  C: /usr/share/fonts/truetype/liberation/LiberationSansNarrow-Regular.ttf

No monospaced truetype font is found. That's not good, is it?

Regards,

Brian.

[fc-match-s (text/plain, attachment)]

[fc-match-a (text/plain, attachment)]

Message #62 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>, 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Fri, 27 Apr 2012 10:09:14 +0200

[Message part 1 (text/plain, inline)]

I've got two good news for you:
1) I was finally able to reproduce your issue on one of my machines
2) I think I found the culprit

Ad 1) I didn't realize that I still had another font installed, the 
Opentype Cantarell font. I was so focussed on Truetype fonts and 
gsfonts-x11 that I simply overlooked it. When I removed this one, I've 
got the exact same symptoms that you described. Since this sounded a 
bit too random, I suspected the culprit to lie in our fontconfig query.

Ad 2) In your cups-filters source copy, in the filters/texttopdf.c 
file, there is line 62 which calls FcPatternAddInteger() and also has 
a comment that this will "guide fc". However, this seems to have 
puzzled the fontconfig pattern, instead.

Please comment out the line and rebuild the package following the 
procedure I described in one of my previous mails. If you feel 
unconfortable editing the file manually (you should), you might as 
well apply the patch I attached to this email (again with "quilt 
import /path/to/patch" and then "quilt push -a"). Please rebuild the 
package and try again.

If this really turns out to be the culprit, I have to check with the 
fontconfig maintainers what's wrong about this command. In any case, 
it did not achieve what it was supposed to do, because most of the 
fonts in the list suggested by fontconfig and printed out by my 
fc-test program were non-monospaced, anyway.

 - Fabian

[no-FcPatternAddInteger.patch (text/x-diff, attachment)]

Message #67 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Fri, 27 Apr 2012 15:35:07 +0100

On Fri 27 Apr 2012 at 10:09:14 +0200, Fabian Greffrath wrote:

> Ad 1) I didn't realize that I still had another font installed, the  
> Opentype Cantarell font. I was so focussed on Truetype fonts and  
> gsfonts-x11 that I simply overlooked it. When I removed this one, I've  
> got the exact same symptoms that you described. Since this sounded a bit 
> too random, I suspected the culprit to lie in our fontconfig query.

I put fonts-cantarell on the system but it did nothing for me. Maybe it
isn't important because it only replicates a part of what you have.

> Please comment out the line and rebuild the package following the  
> procedure I described in one of my previous mails. If you feel  
> unconfortable editing the file manually (you should), you might as well 
> apply the patch I attached to this email (again with "quilt import 
> /path/to/patch" and then "quilt push -a"). Please rebuild the package and 
> try again.

This is important, though. After rebuilding and printing there is now a
/tmp/printout file which pdffonts identifies as having the Liberation
fonts embedded. If it is of interest, here is part of the error_log:

  D [27/Apr/2012:10:58:13 +0100] [Job 39] Page = 612x792; 18,36 to 594,756
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022003l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf:TrueType:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Chosen: /usr/share/fonts/truetype/liberation/LiberationMono-Regular.ttf/0
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022004l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022003l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationMono-Bold.ttf:TrueType:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Chosen: /usr/share/fonts/truetype/liberation/LiberationMono-Bold.ttf/0
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022023l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022003l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationMono-Italic.ttf:TrueType:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Chosen: /usr/share/fonts/truetype/liberation/LiberationMono-Italic.ttf/0
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022024l.pfb:Type 1:
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022023l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022004l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/X11/Type1/n022003l.pfb:Type 1:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Candidate: /usr/share/fonts/truetype/liberation/LiberationMono-BoldItalic.ttf:TrueType:100
  D [27/Apr/2012:10:58:13 +0100] [Job 39] ### Chosen: /usr/share/fonts/truetype/liberation/LiberationMono-BoldItalic.ttf/0
  D [27/Apr/2012:10:58:13 +0100] PID 17922 (/usr/lib/cups/filter/texttopdf) exited with no errors.

> If this really turns out to be the culprit, I have to check with the  
> fontconfig maintainers what's wrong about this command. In any case, it 
> did not achieve what it was supposed to do, because most of the fonts in 
> the list suggested by fontconfig and printed out by my fc-test program 
> were non-monospaced, anyway.

Thank you for perservering with this and for the guidance. I'm available
for any future testing you may need.

Regards,

Brian.

Message #72 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Fri, 27 Apr 2012 16:38:37 +0200

Am 27.04.2012 16:35, schrieb Brian Potkin:
> Thank you for perservering with this and for the guidance. I'm available
> for any future testing you may need.

Please try actual printing with the patched cups-filters package! ;)

 - Fabian

Message #77 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Fri, 27 Apr 2012 16:12:38 +0100

On Fri 27 Apr 2012 at 16:38:37 +0200, Fabian Greffrath wrote:

> Please try actual printing with the patched cups-filters package! ;)

Ye of little faith! The file gets as far as the backend; it actually has
to print . . . . . doesn't it? Ok, done. Success!

Cheers,

Brian.q

Message #82 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>, 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Fri, 27 Apr 2012 19:57:09 +0200

Am Freitag, den 27.04.2012, 16:12 +0100 schrieb Brian Potkin:
> Ye of little faith! The file gets as far as the backend; it actually has
> to print . . . . . doesn't it? Ok, done. Success!

He? Sorry, I don't understand.

Does it print or not? Does this small patch fix the issue for you, even
if only fonts-liberation and gsfonts-x11 are installed?

 - Fabian

Message #87 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Fri, 27 Apr 2012 20:13:46 +0100

On Fri 27 Apr 2012 at 19:57:09 +0200, Fabian Greffrath wrote:

> Does it print or not? Does this small patch fix the issue for you, even
> if only fonts-liberation and gsfonts-x11 are installed?

Sorry for being obscure. Yes, it prints on a real printer in the
circumstances you describe.

Regards,

Brian.

Message #92 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>, 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 30 Apr 2012 11:20:01 +0200

I have raised this issue on the fontconfig upstream mailing list and 
they discovered the trimming of the results in FcfontSort() as the 
culprit, not necessarily the FcPatternAddInteger() call:
<http://lists.freedesktop.org/archives/fontconfig/2012-April/003965.html>

Could you please apply the attached patch against a clean source code 
copy of cups-filters and see if printing will work with this one under 
the given circumstances (i.e. only gsfonts-x11 and fonts-liberation 
installed)?

 - Fabian

Message #97 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>, 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 30 Apr 2012 11:26:51 +0200

[Message part 1 (text/plain, inline)]

Am 30.04.2012 11:20, schrieb Fabian Greffrath:
> Could you please apply the attached patch

This one... :/

[fcfontsort-no-trim.patch (text/x-diff, attachment)]

Message #102 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Brian Potkin <claremont102@gmail.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 30 Apr 2012 14:30:32 +0200

Am 30.04.2012 14:18, schrieb Brian Potkin:
> Printing to file:/ and to my printer is successful. Both pdffonts and
> the paper copy show the Liberation fonts have been used.

Grrreat, thanks again for testing!

I have to clarify one other thing with fontconfig upstream and will 
then send my final patch for cups-filters.

 - Fabian

Message #107 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 30 Apr 2012 13:18:33 +0100

On Mon 30 Apr 2012 at 11:20:01 +0200, Fabian Greffrath wrote:

> Could you please apply the attached patch against a clean source code  
> copy of cups-filters and see if printing will work with this one under  
> the given circumstances (i.e. only gsfonts-x11 and fonts-liberation  
> installed)?

Printing to file:/ and to my printer is successful. Both pdffonts and
the paper copy show the Liberation fonts have been used.

Cheers,

Brian.

Message #112 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: 670055@bugs.debian.org

Cc: control <control@bugs.debian.org>

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Mon, 30 Apr 2012 15:38:00 +0200

[Message part 1 (text/plain, inline)]

tags 670055 -moreinfo -unreproducible +patch
severity 670055 important
thanks

Am 30.04.2012 14:30, schrieb Fabian Greffrath:
> I have to clarify one other thing with fontconfig upstream and will
> then send my final patch for cups-filters.

And here it is.

Till, yould you please apply this patch upstream ASAP?

  - Fabian

[fcfontsort-no-trim.patch (text/x-diff, attachment)]

Message #123 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: Till Kamppeter <till.kamppeter@gmail.com>

Cc: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Wed, 02 May 2012 09:11:20 +0200

Hi Till,

have you seen this?

 - Fabian


Am 30.04.2012 15:38, schrieb Fabian Greffrath:
> tags 670055 -moreinfo -unreproducible +patch
> severity 670055 important
> thanks
>
> Am 30.04.2012 14:30, schrieb Fabian Greffrath:
>> I have to clarify one other thing with fontconfig upstream and will
>> then send my final patch for cups-filters.
>
> And here it is.
>
> Till, yould you please apply this patch upstream ASAP?
>
> - Fabian
>
>

Message #128 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: 670055@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Sun, 13 May 2012 23:31:39 +0200

Erm, could I please get some feedback on my patch from Msg #112? Is
there a specific reason why this is not applied upstream, yet?

 - Fabian

Am Montag, den 30.04.2012, 15:38 +0200 schrieb Fabian Greffrath:
> Am 30.04.2012 14:30, schrieb Fabian Greffrath:
> > I have to clarify one other thing with fontconfig upstream and will
> > then send my final patch for cups-filters.
> And here it is.
> Till, yould you please apply this patch upstream ASAP?

Message #133 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Fabian Greffrath <fabian@greffrath.com>

To: 670055@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#670055: cups-filters: Printing a text file fails when Liberation is the only TrueType font available

Date: Wed, 16 May 2012 13:17:35 +0200

severity 670055 critical
thanks

I know I am getting on your nerves, but without this patch the code will
fail at an assertion introduced in fontconfig 2.9!

Message #140 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Didier Raboud <odyx@debian.org>

To: 670055@bugs.debian.org

Cc: Till Kamppeter <till.kamppeter@gmail.com>, Martin Pitt <mpitt@debian.org>

Subject: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Fri, 18 May 2012 15:51:45 +0200

[Message part 1 (text/plain, inline)]

tags 670055 + pending
thanks

Dear Till and Martin,

I've prepared an upload for cups-filters (versioned as 1.0.18-2) with
Fabian's patch and uploaded it to DELAYED/2. Please feel free to tell me
if I should delay it longer or reschedule it to let it go as is.

Best regards,

OdyX

P.S. I have pushed the change to the packaging repository.

[cups-filters-1.0.18-2-nmu.diff (text/x-diff, attachment)]

Message #147 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Till Kamppeter <till.kamppeter@gmail.com>

To: Didier Raboud <odyx@debian.org>

Cc: 670055@bugs.debian.org, Martin Pitt <mpitt@debian.org>, Tobias Hoffmann <lprint-list@thax.hardliners.org>

Subject: Re: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Fri, 18 May 2012 23:18:47 +0200

For me it looks OK, I would apply it upstream.

Tobias, WDYT? Is this patch on texttopdf OK?

Perhaps it also fixes bug 673289.

   Till

On 05/18/2012 03:51 PM, Didier Raboud wrote:
> tags 670055 + pending
> thanks
>
> Dear Till and Martin,
>
> I've prepared an upload for cups-filters (versioned as 1.0.18-2) with
> Fabian's patch and uploaded it to DELAYED/2. Please feel free to tell me
> if I should delay it longer or reschedule it to let it go as is.
>
> Best regards,
>
> OdyX
>
> P.S. I have pushed the change to the packaging repository.

Message #152 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Tobias Hoffmann <lprint-list@thax.hardliners.org>

To: Till Kamppeter <till.kamppeter@gmail.com>

Cc: Didier Raboud <odyx@debian.org>, 670055@bugs.debian.org, Martin Pitt <mpitt@debian.org>

Subject: Re: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Sat, 19 May 2012 09:51:01 +0200

Till Kamppeter wrote:
> For me it looks OK, I would apply it upstream.
>
> Tobias, WDYT? Is this patch on texttopdf OK?
Looks fine to me.

> Perhaps it also fixes bug 673289.
I hope so...

 Tobias

Message #157 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Didier Raboud <odyx@debian.org>

To: Till Kamppeter <till.kamppeter@gmail.com>

Cc: 670055@bugs.debian.org, Martin Pitt <mpitt@debian.org>, Tobias Hoffmann <lprint-list@thax.hardliners.org>

Subject: Re: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Sat, 19 May 2012 11:51:14 +0200

[Message part 1 (text/plain, inline)]

Le vendredi, 18 mai 2012 23.18:47, Till Kamppeter a écrit :
> For me it looks OK, I would apply it upstream.

Okay, hence re-scheduled to 0-day for immediate upload, thanks for your 
feedback.

Cheers,

OdyX

[signature.asc (application/pgp-signature, inline)]

Message #162 received at 670055-close@bugs.debian.org (full text, mbox, reply):

From: Didier Raboud <odyx@debian.org>

To: 670055-close@bugs.debian.org

Subject: Bug#670055: fixed in cups-filters 1.0.18-2

Date: Sat, 19 May 2012 10:03:23 +0000

Source: cups-filters
Source-Version: 1.0.18-2

We believe that the bug you reported is fixed in the latest version of
cups-filters, which is due to be installed in the Debian FTP archive:

cups-filters_1.0.18-2.debian.tar.gz
  to main/c/cups-filters/cups-filters_1.0.18-2.debian.tar.gz
cups-filters_1.0.18-2.dsc
  to main/c/cups-filters/cups-filters_1.0.18-2.dsc
cups-filters_1.0.18-2_amd64.deb
  to main/c/cups-filters/cups-filters_1.0.18-2_amd64.deb
libcupsfilters-dev_1.0.18-2_amd64.deb
  to main/c/cups-filters/libcupsfilters-dev_1.0.18-2_amd64.deb
libcupsfilters1_1.0.18-2_amd64.deb
  to main/c/cups-filters/libcupsfilters1_1.0.18-2_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 670055@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Didier Raboud <odyx@debian.org> (supplier of updated cups-filters package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2012 15:01:54 +0200
Source: cups-filters
Binary: libcupsfilters1 cups-filters libcupsfilters-dev
Architecture: source amd64
Version: 1.0.18-2
Distribution: unstable
Urgency: low
Maintainer: Debian CUPS Maintainers <pkg-cups-devel@lists.alioth.debian.org>
Changed-By: Didier Raboud <odyx@debian.org>
Description: 
 cups-filters - OpenPrinting CUPS Filters
 libcupsfilters-dev - OpenPrinting CUPS Filters - Development files for the library
 libcupsfilters1 - OpenPrinting CUPS Filters - Shared library
Closes: 670055
Changes: 
 cups-filters (1.0.18-2) unstable; urgency=low
 .
   [ Fabian Greffrath ]
   * Add patch to avoid trimming the results of FcFontSort(), as this may
     miss some reasonable candidates under certain circumstances. BTW,
     fix passing a non-pointer as a pointer to "result". (Closes: #670055)
Checksums-Sha1: 
 1b82046b0e9e2bc3b6a118b6d98cdba32caf68e1 2312 cups-filters_1.0.18-2.dsc
 095ac1503765b73f6157714002f5ad503c4c7835 39651 cups-filters_1.0.18-2.debian.tar.gz
 3b840bd5b2b1c6adf6080bc660cafe56965e652c 64236 libcupsfilters1_1.0.18-2_amd64.deb
 875dbc285935601034aef5c026bf1cd3720c0b3f 387448 cups-filters_1.0.18-2_amd64.deb
 9fd51f73567d148708ebfb5627348325d5c3f261 75380 libcupsfilters-dev_1.0.18-2_amd64.deb
Checksums-Sha256: 
 90b8b82cd872091d329618e5117831ac315e9a207866c882a6d88bc696a80b0f 2312 cups-filters_1.0.18-2.dsc
 74a703ae91cc37d7c822b45f60cb41660abc1354406383f4776c818a564f4d97 39651 cups-filters_1.0.18-2.debian.tar.gz
 59cfdd485f1e1402c7b5d25ca2bbf29c7142741a0e887f28070c5c95e4b5f70b 64236 libcupsfilters1_1.0.18-2_amd64.deb
 c92f88b47a101483c3ab9ad97ba163d40595f1c88b56bc006d111c22a21b1692 387448 cups-filters_1.0.18-2_amd64.deb
 7eb435d17c8565992b2d34b7f474549a67c0ef57bbaa8a870432a5e44a79ad31 75380 libcupsfilters-dev_1.0.18-2_amd64.deb
Files: 
 6c25a96b4f53a645d71b36dd52d1f071 2312 net optional cups-filters_1.0.18-2.dsc
 52fdfd7e2fa4c6075453049e3f5beaf0 39651 net optional cups-filters_1.0.18-2.debian.tar.gz
 e5010687d1910fc9533df7af237ef1ff 64236 libs optional libcupsfilters1_1.0.18-2_amd64.deb
 09fdfc3659da968871294006f94d518f 387448 net optional cups-filters_1.0.18-2_amd64.deb
 4a591ee6861dcbf3526dd9461595e699 75380 libdevel optional libcupsfilters-dev_1.0.18-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQGcBAEBCAAGBQJPtlAWAAoJEIvPpx7KFjRVSHUL/1sMToI1ys5s6f41UjBeRiWf
NTphSgEc4puuTRdnEUu9fqCHXKk/56Ta7X7ABlc14UP+fJ1bsPLtLX5ziAm88wwX
ooveckdnjR6oHuTMv0Yl3HmuVjuFmlZqXJ+ThnObMFadAN2OHQg2MQdFiu8vxeyf
gAhTpBX1R0QmTI+IxpWHpA+ojDjQSbx6fSZZX/xBZkhs8kWyWTY7PiD9F7veozbY
smWRIfIitdFvJSHbkOy/6Jkg8QRS0eOI/+bsBL3rfNXaAgEuV0r3jqUtxAdDdkXa
vvwSZwWacZwb9qvIpk/40c8NcFdB56lwyK/za4pjXvhgxVSDhKuEGPNrTnx0fOrS
nUCrrkK4pdsD5QgzdCPiihCxmyw98g+LkmkZy8sBbun0ZQcAvt5yqOxUUlNW/OPE
sgqJfIXWZ3E//ZQyg+9TH5e4dI7GiSTJCNGKRlOQTrdrGwNAUWRZ/5tv2n9YTIt4
ILe0crsGHEbMRrzw5XQb0DcMxF7GuJLgFpc2VvplSQ==
=73kp
-----END PGP SIGNATURE-----

Message #167 received at 670055@bugs.debian.org (full text, mbox, reply):

From: "Fabian Greffrath" <fabian@greffrath.com>

To: "Tobias Hoffmann" <lprint-list@thax.hardliners.org>, 670055@bugs.debian.org, 673289@bugs.debian.org, "Paul Menzel" <pm.debian@googlemail.com>

Cc: "Till Kamppeter" <till.kamppeter@gmail.com>, "Didier Raboud" <odyx@debian.org>, "Martin Pitt" <mpitt@debian.org>

Subject: Re: Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Mon, 21 May 2012 22:57:18 +0200

>> Tobias, WDYT? Is this patch on texttopdf OK?
> Looks fine to me.

Thanks for finally applying it!

>> Perhaps it also fixes bug 673289.
> I hope so...

Let's find it out.

Paul, is the crash you reported in #673289 reproducable with cups-filters
1.0.18-2?

 - Fabian

Message #172 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Paul Menzel <pm.debian@googlemail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: Tobias Hoffmann <lprint-list@thax.hardliners.org>, 670055@bugs.debian.org, 673289@bugs.debian.org, Till Kamppeter <till.kamppeter@gmail.com>, Didier Raboud <odyx@debian.org>, Martin Pitt <mpitt@debian.org>

Subject: Re: Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Tue, 22 May 2012 00:18:17 +0200

[Message part 1 (text/plain, inline)]

fixed 673289 1.0.18-2
quit


Dear Fabian,


thank you for CCing me.

Till, Tobias, please always put the reporter and responders(?) into CC.
Otherwise they will (unfortunately) not be notified.


Am Montag, den 21.05.2012, 22:57 +0200 schrieb Fabian Greffrath:
> >> Tobias, WDYT? Is this patch on texttopdf OK?
> > Looks fine to me.
> 
> Thanks for finally applying it!

Thank you from me too.

> >> Perhaps it also fixes bug 673289.
> > I hope so...
> 
> Let's find it out.
> 
> Paul, is the crash you reported in #673289 reproducable with cups-filters
> 1.0.18-2?

No it is not. I can no longer reproduce it.

        lpr -PCUPS-PDF-Printer /tmp/test.txt

and

        CHARSET=utf-8 /usr/lib/cups/filter/texttopdf 1 user title 1 "PageSize=A4" test.txt > out.pdf

work fine.

As a side not Evince has problems displaying the output from CUPS-PDF.
The text is not readable. Xpdf displays everything correctly though. So
that issue is a separate bug in Evince I guess.

I mark this bug as fixed in 1.0.18-2. I am not closing it yet since I do
not know if you want it merged with #670055 or not.


Thanks,

Paul

[signature.asc (application/pgp-signature, inline)]

Message #177 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Paul Menzel <pm.debian@googlemail.com>

To: Fabian Greffrath <fabian@greffrath.com>

Cc: Tobias Hoffmann <lprint-list@thax.hardliners.org>, 670055@bugs.debian.org, 673289@bugs.debian.org, Till Kamppeter <till.kamppeter@gmail.com>, Didier Raboud <odyx@debian.org>, Martin Pitt <mpitt@debian.org>

Subject: Re: Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Tue, 22 May 2012 00:33:18 +0200

[Message part 1 (text/plain, inline)]

Dear Debian folks,


Am Dienstag, den 22.05.2012, 00:18 +0200 schrieb Paul Menzel:
> fixed 673289 1.0.18-2
> quit

> thank you for CCing me.
> 
> Till, Tobias, please always put the reporter and responders(?) into CC.
> Otherwise they will (unfortunately) not be notified.
> 
> 
> Am Montag, den 21.05.2012, 22:57 +0200 schrieb Fabian Greffrath:
> > >> Tobias, WDYT? Is this patch on texttopdf OK?
> > > Looks fine to me.
> > 
> > Thanks for finally applying it!
> 
> Thank you from me too.
> 
> > >> Perhaps it also fixes bug 673289.
> > > I hope so...
> > 
> > Let's find it out.
> > 
> > Paul, is the crash you reported in #673289 reproducable with cups-filters
> > 1.0.18-2?
> 
> No it is not. I can no longer reproduce it.
> 
>         lpr -PCUPS-PDF-Printer /tmp/test.txt
> 
> and
> 
>         CHARSET=utf-8 /usr/lib/cups/filter/texttopdf 1 user title 1 "PageSize=A4" test.txt > out.pdf
> 
> work fine.
> 
> As a side not Evince has problems displaying the output from CUPS-PDF.
> The text is not readable. Xpdf displays everything correctly though. So
> that issue is a separate bug in Evince I guess.

Just more information. This seems to be a CUPS-PDF issue.

        $ pdffonts CUPS-PDF/test.pdf
        name                                 type              emb sub uni object ID
        ------------------------------------ ----------------- --- --- --- ---------
        [none]                               Type 3            yes no  yes     12  0
        $ pdffonts /tmp/out.pdf 
        name                                 type              emb sub uni object ID
        ------------------------------------ ----------------- --- --- --- ---------
        JMQJEJ+FreeMono                      CID TrueType      yes yes no      11  0

But I think to remember, someone wrote in another bug report that
CUPS-PDF is not meant for printing text. Still it is strange that Xpdf
works fine. If you gave me a hint where to assign such a report to, I
would be very thankful.

> I mark this bug as fixed in 1.0.18-2. I am not closing it yet since I do
> not know if you want it merged with #670055 or not.


Thanks,

Paul

[signature.asc (application/pgp-signature, inline)]

Message #182 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Tobias Hoffmann <lprint-list@thax.hardliners.org>

To: Paul Menzel <pm.debian@googlemail.com>

Cc: Fabian Greffrath <fabian@greffrath.com>, 670055@bugs.debian.org, 673289@bugs.debian.org, Till Kamppeter <till.kamppeter@gmail.com>, Didier Raboud <odyx@debian.org>, Martin Pitt <mpitt@debian.org>

Subject: Re: Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Tue, 22 May 2012 13:39:20 +0200

Paul Menzel wrote:
>> As a side not Evince has problems displaying the output from CUPS-PDF.
>> The text is not readable. Xpdf displays everything correctly though. So
>> that issue is a separate bug in Evince I guess.
>>     
> Just more information. This seems to be a CUPS-PDF issue.
>
>         $ pdffonts CUPS-PDF/test.pdf
>         name                                 type              emb sub uni object ID
>         ------------------------------------ ----------------- --- --- --- ---------
>         [none]                               Type 3            yes no  yes     12  0
>         $ pdffonts /tmp/out.pdf 
>         name                                 type              emb sub uni object ID
>         ------------------------------------ ----------------- --- --- --- ---------
>         JMQJEJ+FreeMono                      CID TrueType      yes yes no      11  0
>
> But I think to remember, someone wrote in another bug report that
> CUPS-PDF is not meant for printing text. Still it is strange that Xpdf
> works fine.
Ok. I've had another look. My emtpy PDF came from the very bug here 
reported (the fix is not in testing yet); I've copied my bzr build to 
the system folder, and voila...:

Xpdf spits out a lot of "Error: Bad bounding box in Type 3 glyph" on the 
CUPS-PDF file. This is consistent with "Type 3" in the font list.
Evince-gtk does work here, BUT it prints:
   *** BUG ***
   In pixman_region32_init_rect: Invalid rectangle passed
   Set a breakpoint on '_pixman_log_error' to debug
which probably causes empty pages in some other versions of evince 
and/or pixman/cairo.

So why are Type 3 fonts used?
 I [22/May/2012:13:04:51 +0200] [Job 784] Started filter 
/usr/lib/cups/filter/texttopdf (PID 20424)
 I [22/May/2012:13:04:51 +0200] [Job 784] Started filter 
/usr/lib/cups/filter/pdftopdf (PID 20425)
 I [22/May/2012:13:04:51 +0200] [Job 784] Started filter 
/usr/lib/cups/filter/pdftops (PID 20426)
 I [22/May/2012:13:04:51 +0200] [Job 784] Started backend 
/usr/lib/cups/backend/cups-pdf (PID 20427)
That means: Text is converted by texttopdf (fine).
This is sent through pdftopdf (still ok).
Then it is converted to PS by pdftops und converted back to PDF by 
cups-pdf (unwanted); also the font is converted to Type 3 by one of 
these two filters (not nice), but the routine outputs Type 3-bounding 
boxes the pdf consumer regards as wrong (bad), which is either a bug in 
the pdf consumer ("poppler"/...) or the producer (ghostscript for both 
pdftops and cups-pdf over here; pdftops(cups) seems to also be able to 
call pdftops(poppler-tools)  which did not produce Type3 on a quick 
test...).

> If you gave me a hint where to assign such a report to, I
> would be very thankful.
Hmm, I don't really know, but the cups-filters package has a bugtracker 
at https://bugs.linuxfoundation.org/  (under the OpenPrinting product). 
But just another debian bug would work equally well ...
Till?

 Tobias

Message #187 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Till Kamppeter <till.kamppeter@gmail.com>

To: Tobias Hoffmann <lprint-list@thax.hardliners.org>

Cc: Paul Menzel <pm.debian@googlemail.com>, Fabian Greffrath <fabian@greffrath.com>, 670055@bugs.debian.org, 673289@bugs.debian.org, Didier Raboud <odyx@debian.org>, Martin Pitt <mpitt@debian.org>

Subject: Re: Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Tue, 22 May 2012 14:14:10 +0200

On 05/22/2012 01:39 PM, Tobias Hoffmann wrote:
> Hmm, I don't really know, but the cups-filters package has a bugtracker
> at https://bugs.linuxfoundation.org/ (under the OpenPrinting product).
> But just another debian bug would work equally well ...
> Till?

Tobias, if this needs to be fixed in the texttopdf filter a bug on 
https://bugs.linuxfoundation.org/ can be filed. If it is a problem of 
Debian's packaging or Debian shipping a broken font or not shipping a 
required font then open a Debian bug.

   Till

Message #192 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Tobias Hoffmann <lprint-list@thax.hardliners.org>

To: Till Kamppeter <till.kamppeter@gmail.com>

Cc: Paul Menzel <pm.debian@googlemail.com>, Fabian Greffrath <fabian@greffrath.com>, 670055@bugs.debian.org, 673289@bugs.debian.org, Didier Raboud <odyx@debian.org>, Martin Pitt <mpitt@debian.org>

Subject: Re: Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Tue, 22 May 2012 15:11:01 +0200

Till Kamppeter wrote:
> Tobias, if this needs to be fixed in the texttopdf filter a bug on 
> https://bugs.linuxfoundation.org/ can be filed. If it is a problem of 
> Debian's packaging or Debian shipping a broken font or not shipping a 
> required font then open a Debian bug.
Well, it's still not clear, who should fix what:

1. cups-pdf should probably announce that it can not only process PS, 
but also PDF. I'm not sure if the current cups-filter architecture 
handles this case well. This bug would be one of cups-pdf or cups-filter(?).
2. It's unclear to me what the policy regarding pdftops is wrt. to using 
popper vs. ghostscript as converting agent. gs generates Type 3 (which 
causes problems), poppler does not. This can be fixed in pdftops, i.e. 
cups-filter, (use poppler tools in this case), or ghostscript (don't 
generate Type 3 -- there might be some commandline switches)
3. The issue, that the Type 3 bounding boxes generated by ghostscript 
are deemed bad by poppler/evince. The experts from ghostscript and 
poppler have to determine who is wrong (it might even be caused by the 
original font file). Therefore this is either a poppler/evince, 
ghostscript or font bug.

I'm not sure if any of these points could even be worked around by 
texttopdf, i.e. no bug in textopdf, AFAICS.
I don't have the spare time to take steps 1.-3. further myself, so if 
anyone would take over from here?

 Tobias

Message #197 received at 670055@bugs.debian.org (full text, mbox, reply):

From: Till Kamppeter <till.kamppeter@gmail.com>

To: Tobias Hoffmann <lprint-list@thax.hardliners.org>

Cc: Paul Menzel <pm.debian@googlemail.com>, Fabian Greffrath <fabian@greffrath.com>, 670055@bugs.debian.org, 673289@bugs.debian.org, Didier Raboud <odyx@debian.org>, Martin Pitt <mpitt@debian.org>, Chris Liddell <chris.liddell@artifex.com>

Subject: Re: Bug#670055: cups-filters: diff for version 1.0.18-2 uploaded to DELAYED/2 for #670055

Date: Tue, 22 May 2012 16:06:15 +0200

On 05/22/2012 03:11 PM, Tobias Hoffmann wrote:
> Well, it's still not clear, who should fix what:
>
> 1. cups-pdf should probably announce that it can not only process PS,
> but also PDF. I'm not sure if the current cups-filter architecture
> handles this case well. This bug would be one of cups-pdf or
> cups-filter(?).

This is a cups-pdf problem. I have even fixed it once by doing some 
slight changes on cups-pdf, making the PPD file accepting both PDF and 
PostScript as input and modifying the backend script to skip Ghostscript 
if the input is already PDF. Upstream did not accept this patch as one 
can modify the output by a variety of options in the config file and 
these options are implemented via Ghostscript.

I suggest then to do a slightly different approach, only skipping 
Ghostscript if the settings in the config file are the default settings 
and otherwise using Ghostscript also with PDF input, simply feeding PDF 
into Ghostscript.

See

debian/patches/70_cups-pdf_support-pdf-workflow.patch

in cups-pdf 2.5.0-17 on

https://launchpad.net/ubuntu/+source/cups-pdf/2.5.0-17

> 2. It's unclear to me what the policy regarding pdftops is wrt. to using
> popper vs. ghostscript as converting agent. gs generates Type 3 (which
> causes problems), poppler does not. This can be fixed in pdftops, i.e.
> cups-filter, (use poppler tools in this case), or ghostscript (don't
> generate Type 3 -- there might be some commandline switches)

For pdftops I was always tending to use Ghostscript as Ghostscript has 
once better color management and is designed more with printing in mind. 
At the release of Ubuntu Precise (12.04) I have found out that 
Ghostscript's PS output has problems with several PostScript printers 
due to bugs in the printer's PS interpreters. I added some workarounds 
to the pdftops filter for that. Which PostScript consumers do not like 
Type 3 fonts? Should I make Ghostscript only sending Type 2 fonts?

Chris, is there a command line switch to make Ghostscript's "ps2write" 
device only sending Type 2 fonts?

> 3. The issue, that the Type 3 bounding boxes generated by ghostscript
> are deemed bad by poppler/evince. The experts from ghostscript and
> poppler have to determine who is wrong (it might even be caused by the
> original font file). Therefore this is either a poppler/evince,
> ghostscript or font bug.
>

Chris, can it be that there is a bug in Ghostscript?

   Till

Send a report that this bug log contains spam.