Bug#868360: cups-filters-core-drivers: driverless sets bizarre 600x2 resolution

2017-07-14 Thread brian m. carlson 
Package: cups-filters-core-drivers
Version: 1.14.1-1
Severity: normal

I have a Brother MFC-9340CDW printer on the local LAN.  When using the
driverless configuration, the resolution is set to 600x2 dpi, resulting
in the printer printing literally two lines on the page.  The resolution
of the printer is either 600x600 or 600x2400 dpi.

The output of the command is below.  You can see that it recognizes the
correct resolution, but emits the incorrect one in the PPD.  I suspect
something is getting truncated somewhere.

genre ok % /usr/lib/cups/driver/driverless cat ipp://copper.local:631/ipp/print
DEBUG2: Attr: attributes-charset
DEBUG2: Value: utf-8
DEBUG2: Keyword: utf-8
DEBUG2: Attr: attributes-natural-language
DEBUG2: Value: en-us
DEBUG2: Keyword: en-us
DEBUG2: Attr: copies-default
DEBUG2: Value: 1
DEBUG2: Keyword: (null)
DEBUG2: Attr: finishings-default
DEBUG2: Value: none
DEBUG2: Keyword: (null)
DEBUG2: Attr: media-default
DEBUG2: Value: na_letter_8.5x11in
DEBUG2: Keyword: na_letter_8.5x11in
DEBUG2: Attr: media-col-default
DEBUG2: Value: {media-type=stationery media-size={x-dimension=21590 
y-dimension=27940} media-bottom-margin=432 media-left-margin=432 
media-right-margin=432 media-top-margin=432 media-source=auto}
DEBUG2: Keyword: (null)
DEBUG2: Attr: orientation-requested-default
DEBUG2: Value: portrait
DEBUG2: Keyword: (null)
DEBUG2: Attr: output-bin-default
DEBUG2: Value: face-down
DEBUG2: Keyword: face-down
DEBUG2: Attr: output-mode-default
DEBUG2: Value: color
DEBUG2: Keyword: color
DEBUG2: Attr: print-quality-default
DEBUG2: Value: normal
DEBUG2: Keyword: (null)
DEBUG2: Attr: printer-resolution-default
DEBUG2: Value: 600dpi
DEBUG2: Keyword: (null)
DEBUG2: Attr: sides-default
DEBUG2: Value: one-sided
DEBUG2: Keyword: one-sided
DEBUG2: Attr: print-color-mode-default
DEBUG2: Value: color
DEBUG2: Keyword: color
DEBUG2: Attr: copies-supported
DEBUG2: Value: 1-1
DEBUG2: Keyword: (null)
DEBUG2: Attr: finishings-supported
DEBUG2: Value: none
DEBUG2: Keyword: (null)
DEBUG2: Attr: media-supported
DEBUG2: Value: 
iso_a4_210x297mm,na_letter_8.5x11in,na_legal_8.5x14in,na_executive_7.25x10.5in,iso_a5_148x210mm,iso_a6_105x148mm,iso_b5_176x250mm,jis_b5_182x257mm,na_number-10_4.125x9.5in,iso_dl_110x220mm,iso_c5_162x229mm,na_monarch_3.875x7.5in,na_index-3x5_3x5in,om_folio_210x330mm,custom_min_76.2x127mm,custom_max_215.9x355.6mm
DEBUG2: Keyword: iso_a4_210x297mm
DEBUG2: Keyword: na_letter_8.5x11in
DEBUG2: Keyword: na_legal_8.5x14in
DEBUG2: Keyword: na_executive_7.25x10.5in
DEBUG2: Keyword: iso_a5_148x210mm
DEBUG2: Keyword: iso_a6_105x148mm
DEBUG2: Keyword: iso_b5_176x250mm
DEBUG2: Keyword: jis_b5_182x257mm
DEBUG2: Keyword: na_number-10_4.125x9.5in
DEBUG2: Keyword: iso_dl_110x220mm
DEBUG2: Keyword: iso_c5_162x229mm
DEBUG2: Keyword: na_monarch_3.875x7.5in
DEBUG2: Keyword: na_index-3x5_3x5in
DEBUG2: Keyword: om_folio_210x330mm
DEBUG2: Keyword: custom_min_76.2x127mm
DEBUG2: Keyword: custom_max_215.9x355.6mm
DEBUG2: Attr: media-col-supported
DEBUG2: Value: 
media-type,media-size,media-top-margin,media-left-margin,media-right-margin,media-bottom-margin,media-source
DEBUG2: Keyword: media-type
DEBUG2: Keyword: media-size
DEBUG2: Keyword: media-top-margin
DEBUG2: Keyword: media-left-margin
DEBUG2: Keyword: media-right-margin
DEBUG2: Keyword: media-bottom-margin
DEBUG2: Keyword: media-source
DEBUG2: Attr: orientation-requested-supported
DEBUG2: Value: portrait,landscape
DEBUG2: Keyword: (null)
DEBUG2: Keyword: (null)
DEBUG2: Attr: output-bin-supported
DEBUG2: Value: face-down
DEBUG2: Keyword: face-down
DEBUG2: Attr: output-mode-supported
DEBUG2: Value: color,auto,monochrome
DEBUG2: Keyword: color
DEBUG2: Keyword: auto
DEBUG2: Keyword: monochrome
DEBUG2: Attr: print-quality-supported
DEBUG2: Value: normal,high
DEBUG2: Keyword: (null)
DEBUG2: Keyword: (null)
DEBUG2: Attr: printer-resolution-supported
DEBUG2: Value: 600dpi,2400x600dpi
DEBUG2: Keyword: (null)
DEBUG2: Keyword: (null)
DEBUG2: Attr: sides-supported
DEBUG2: Value: one-sided,two-sided-long-edge,two-sided-short-edge
DEBUG2: Keyword: one-sided
DEBUG2: Keyword: two-sided-long-edge
DEBUG2: Keyword: two-sided-short-edge
DEBUG2: Attr: print-color-mode-supported
DEBUG2: Value: auto,color,monochrome
DEBUG2: Keyword: auto
DEBUG2: Keyword: color
DEBUG2: Keyword: monochrome
DEBUG2: Attr: generated-natural-language-supported
DEBUG2: Value: en,fr
DEBUG2: Keyword: en
DEBUG2: Keyword: fr
DEBUG2: Attr: printer-uri-supported
DEBUG2: Value: ipp://copper.local./ipp/print
DEBUG2: Keyword: ipp://copper.local./ipp/print
DEBUG2: Attr: uri-security-supported
DEBUG2: Value: none
DEBUG2: Keyword: none
DEBUG2: Attr: uri-authentication-supported
DEBUG2: Value: none
DEBUG2: Keyword: none
DEBUG2: Attr: printer-name
DEBUG2: Value: copper[en]
DEBUG2: Keyword: copper
DEBUG2: Attr: printer-location
DEBUG2: Value: [en]
DEBUG2: Keyword:
DEBUG2: Attr: printer-info
DEBUG2: Value: Brother MFC-9340CDW[en]
DEBUG2: Keyword: Brother MFC-9340CDW
DEBUG2: Attr: printer-make-and-model
DEBUG2: Value: Brother

Bug#868316: cups-bsd: lpr does not print with "DefaultPolicy authenticated" in cupsd.conf

2017-07-14 Thread Brian Potkin 
Thank you for your report, Christoph.


On Fri 14 Jul 2017 at 15:00:26 +0200, Christoph Pleger wrote:

> I do not know if it is a problem with the lpr program from cups-bsd or with
> the cups daemon itself, but with "DefaultPolicy authenticated" in
> cupsd.conf, lpr does not print, but the job remains in the print queue for a
> while and then is removed.

You could try using lp to print but I cannot see that producing any
different an outcome.

We'll need an error_log; the Printing section of the wiki will guide
you in getting one. Compress it with gzip and send it to #868316.
Also attach your cupsd.conf and give the printer make and model.

Regards,

Brian.

Bug#858570: cups-filters: FTBFS: file goo/gmem.h is missing

2017-07-14 Thread Till Kamppeter 

On 07/14/2017 11:38 AM, Roland Hieber wrote:

Hi,

On 13.07.2017 16:55, Till Kamppeter wrote:

I am Till Kamppeter, leader of the OpenPrinting project and also of
cups-filters which is part of OpenPrinting.

The upstream bug tracker is the Linux Foundation one, bugs and feature
requests in cups-filters are filed under the product OpenPrinting and
the component cups-filters.

Here I have regularly received bug reports, fixed bugs, and reviewed and
applied patches.


Yes, I've seen this (it took a while to find the bug tracker on the 
oprnprinting.org page). I've looked at multiple of the cups-filters bugs 
and noticed that none of them had more than one message, therefore my 
thought about the project being dead. As this is not the case, like you 
say, I will report bugs for the patches I have, thank you :)


  - Roland


Probably you only saw only the message counters and not the actual bug 
reports and the counters seem to not include the original posting (bug 
description) but only the actual answers. So these means there was one 
answer to the original posting. And this is correct, as most of the 
reports are simple things, where, without needing discussion, I applied 
the suggested fix or patch and posted one answer telling that I have 
done so. So only worry if Bugzilla tells you about zero messages.


   Till

Bug#868316: cups-bsd: lpr does not print with "DefaultPolicy authenticated" in cupsd.conf

2017-07-14 Thread Christoph Pleger 

Package: cups-bsd
Version: 2.2.1-8

Dear maintainers,

I do not know if it is a problem with the lpr program from cups-bsd or 
with the cups daemon itself, but with "DefaultPolicy authenticated" in 
cupsd.conf, lpr does not print, but the job remains in the print queue 
for a while and then is removed.


Regards
  Christoph