Bug#879171: cups: failed to recognize a driver of CP310dm

2017-10-26 Thread Atsuhito Kohda
Hi Brian,

On Thu, 26 Oct 2017 12:01:00 +0100, Brian Potkin wrote:

> Do you mean "CP310 dw"? This printer:
> 
>  http://news.fujixerox.com/image_library/detail/_imgid_000316/

Yes, sorry for my inaccuracy.

> What do you mean by "failed to recognize driver of CP310dm"?

I got printer driver (fxlinuxprint_1.1.2-1_amd64.deb)
from FujiXerox site; http://www.fujixerox.co.jp/download/eng/
(in fact, I accessed a Japanese page of it).
It installed /usr/share/ppd/FujiXerox/fxlinuxprint.ppd.gz

When I installed CP310 with cups (web interface), I selected
PPD and a file fxlinuxprint.ppd.gz. But after installation,
cups shows a printer driver of CP310 as "Local Raw Printer".
And, of course, I can't print with CP310.

> There is a PPD for your printer in /etc/cups/ppd. Please run the
> commands (as root)
> 
>  cupsfilter -p  -m printer/foo -e /etc/nsswitch  2>log.stretch
>  cupsfilter -p  -m printer/foo -e /etc/nsswitch  2>log.unstable
> 
> on stretch and an updated unstable.
> 
> Attach log.stretch and log.unstable to your next mail to the bug
> report.

I update cups 2.2.5-2 and set CP310 but it seems there is
no corresponding PPD in /etc/cups/ppd/

$ LANG=C ls -l /etc/cups/ppd/
total 80
-rw-r- 1 root lp 24814 Oct 17 08:59 CP310_dw.ppd
-rw-r- 1 root lp 24814 Oct 17 08:59 CP310_dw.ppd.O
-rw-r- 1 root lp 10713 Oct 13 06:52 ipsio.ppd
-rw-r- 1 root lp 10705 Jul 24 07:12 ipsio.ppd.O

I guess CP310_dw is a PPD when I installed cups 2.2.4-7.
So I can't generate log.unstable and attatch only log.stretch.
If I misunderstand anything, please let me know.

Thanks for your response.
2017-10-27(Fri)

-- 
 **
 Atsuhito Kohda
 Math. Meth. in Sci., Tokushima Univ.
 atsuhito_k AT tokushima-u.ac.jp



Bug#879171: cups: failed to recognize a driver of CP310dm

2017-10-26 Thread Atsuhito Kohda
Hi Brian,

Sorry, I forgot to attach log.stretch.
Here it is.

Best regards,   2017-10-27(Fri)

-- 
 **
 Atsuhito Kohda
 Math. Meth. in Sci., Tokushima Univ.
 atsuhito_k AT tokushima-u.ac.jp
cupsfilter: File "/usr/lib/cups/filter/pdftopjlfx" permissions OK 
(040755/uid=0/gid=0).
cupsfilter: File "/usr/lib/cups/filter/pstopdffx" permissions OK 
(040755/uid=0/gid=0).
cupsfilter: File "/usr/lib/cups/filter/commandtops" permissions OK 
(040755/uid=0/gid=0).
cupsfilter: Unable to determine MIME type of "/etc/nsswitch".


Bug#873606: cups: 2.2.4 stopped being able to interact with our cups server

2017-10-26 Thread Julian Wollrath
Hi Brian,

> This bug is against cups 2.2.4-1. Perhaps I was unclear. I suggest
> testing the behaviour of 'lpstat -a' and the commands Samuel used
> with unstable's cups 2.2.5-2.
now I understand, thanks for the clarification. 2.2.5-2 changes nothing
for me.

Cheers,
Julian

> 
> Cheers,
> 
> Brian.



-- 
 ()  ascii ribbon campaign - against html e-mail 
 /\- against proprietary attachments



Bug#879491: marked as done (cups: printing 3 copies of every page)

2017-10-26 Thread Debian Bug Tracking System
Your message dated Thu, 26 Oct 2017 12:35:34 +0100
with message-id <26102017121954.ac789b176...@desktop.copernicus.org.uk>
and subject line Re: Bug#879491: cups: printing 3 copies of every page
has caused the Debian Bug report #879491,
regarding cups: printing 3 copies of every page
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 ow...@bugs.debian.org
immediately.)


-- 
879491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 2.2.5-2
Severity: important

(I'm labelling this as "important" because it's wasting large amounts
of paper.)

This is a weird bug, and I have little idea how to track down the
cause.

About a week or so ago, on my Debian testing system, printing commands
started producing three copies of every page on my local printer (so a
2-page document would come out at 3 copies of page 1 followed by 3
copies of page 2).  This is the case in at least all of the following
circumstances:

* Connect the printer with a USB cable, print via usb://...
* Connect the printer with via ethernet, print via dnssd://...
* Print from evince
* Print using lpr (eg: echo hello | lpr)
* Going to http://localhost:603/ and doing Maintenance -> Print Test Page

However, going to http://localhost:603/ and doing Maintenance -> Print
SELF Test Page only produces a single page of output!

I have updated cups to the latest version today (2.2.5-2), and that
has made no difference, and nor has deleting the printer from CUPS and
reinstalling it.  The PPD files have not changed in about a year
(except for the uninstalling and reinstalling, and even that installed
an identical copy to the existing PPD file).

So I'm at a bit of a loss as to the cause of this.  I also don't see
anything obvious in the log files, but I may be missing something.

Any suggestions?

Thanks!

   Julian

-- System Information:
Debian Release: buster/sid
  APT prefers stretch
  APT policy: (500, 'stretch'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups depends on:
ii  cups-client2.2.5-2
ii  cups-common2.2.5-2
ii  cups-core-drivers  2.2.5-2
ii  cups-daemon2.2.5-2
ii  cups-filters   1.17.9-1
ii  cups-ppdc  2.2.5-2
ii  cups-server-common 2.2.5-2
ii  debconf [debconf-2.0]  1.5.64
ii  ghostscript9.22~dfsg-1
ii  libavahi-client3   0.7-3
ii  libavahi-common3   0.7-3
ii  libc-bin   2.24-17
ii  libc6  2.24-17
ii  libcups2   2.2.5-2
ii  libcupscgi12.2.5-2
ii  libcupsimage2  2.2.5-2
ii  libcupsmime1   2.2.5-2
ii  libcupsppdc1   2.2.5-2
ii  libgcc11:7.2.0-11
ii  libstdc++6 7.2.0-11
ii  libusb-1.0-0   2:1.0.21-2
ii  poppler-utils  0.57.0-2
ii  procps 2:3.3.12-3

Versions of packages cups recommends:
ii  avahi-daemon 0.7-3
ii  colord   1.3.3-2
ii  cups-filters [ghostscript-cups]  1.17.9-1
ii  printer-driver-gutenprint5.2.13-1

Versions of packages cups suggests:
ii  cups-bsd   2.2.5-2
pn  cups-pdf   
ii  foomatic-db-compressed-ppds [foomatic-db]  20171012-1
pn  hplip  
ii  printer-driver-hpcups  3.17.9+repack0-1
ii  smbclient  2:4.6.7+dfsg-2
ii  udev   235-2

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: lpd, socket, usb, snmp, dnssd
--- End Message ---
--- Begin Message ---
On Wed 25 Oct 2017 at 22:35:20 +0100, Julian Gilbey wrote:

> On Wed, Oct 25, 2017 at 08:08:04PM +0100, Brian Potkin wrote:

[Snip]

> > Can this changed be pinned down to any particular version of cups or
> > cups-filters? Or something you altered in cupsd.conf (for example) at
> > that time?
> 
> The upgrades I've done in October were as follows:
> 
> Oct 8:
> [UPGRADE] cups-browsed:amd64 1.16.4-1+b2 -> 1.17.8-1
> [UPGRADE] cups-filters:amd64 1.16.4-1+b2 -> 1.17.8-1
> [UPGRADE] cups-filters-core-drivers:amd64 1.16.4-1+b2 -> 1.17.8-1
> [UPGRADE] libcupsfilters-dev:amd64 1.16.4-1+b2 -> 1.17.8-1
> 

Bug#879171: cups: failed to recognize a driver of CP310dm

2017-10-26 Thread Brian Potkin
Hello Atsuhito. Thank you for your report.


On Fri 20 Oct 2017 at 09:30:09 +0900, Atsuhito Kohda wrote:

> Package: cups
> Version: 2.2.5-2
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> After upgrading to 2.2.5, I can't set up a printer with
> cups because cups failed to recognize driver of CP310dm.
> CP310dm is a (japanese model,perhaps) printer of FujiXerox.

Do you mean "CP310 dw"? This printer:

 http://news.fujixerox.com/image_library/detail/_imgid_000316/

What do you mean by "failed to recognize driver of CP310dm"?
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Downgrading to 2.2.4-7 fixed the problem.
> 
>* What was the outcome of this action?
>* What outcome did you expect instead?
> I expect cups 2.2.5 should recognize CP310dm.
> 
> Thanks for your maintenance.

There is a PPD for your printer in /etc/cups/ppd. Please run the
commands (as root)

 cupsfilter -p  -m printer/foo -e /etc/nsswitch  2>log.stretch
 cupsfilter -p  -m printer/foo -e /etc/nsswitch  2>log.unstable

on stretch and an updated unstable.

Attach log.stretch and log.unstable to your next mail to the bug
report.

Regards,

Brian.



Bug#873606: cups: 2.2.4 stopped being able to interact with our cups server

2017-10-26 Thread Brian Potkin
On Thu 26 Oct 2017 at 11:29:48 +0200, Julian Wollrath wrote:

> Hi Brian,
> 
> > Samuel and Julian, please take a look at #877888 and let us know if it
> > fixes things.
> I do not have a ~/.cups folder nor any lpoptions
> (in /etc/cups/lpoptions or somewhere else) nor any PRINTER
> environment variables set. Only the afore mentioned entry
> in /etc/cups/client.conf. So I do not see how 877888 could relate to the
> problem and I do not see, what I could try from the suggestions in that
> bug.

This bug is against cups 2.2.4-1. Perhaps I was unclear. I suggest
testing the behaviour of 'lpstat -a' and the commands Samuel used
with unstable's cups 2.2.5-2.

Cheers,

Brian.



Bug#873606: cups: 2.2.4 stopped being able to interact with our cups server

2017-10-26 Thread Julian Wollrath
Hi Brian,

> Samuel and Julian, please take a look at #877888 and let us know if it
> fixes things.
I do not have a ~/.cups folder nor any lpoptions
(in /etc/cups/lpoptions or somewhere else) nor any PRINTER
environment variables set. Only the afore mentioned entry
in /etc/cups/client.conf. So I do not see how 877888 could relate to the
problem and I do not see, what I could try from the suggestions in that
bug.


Cheers,
Julian


-- 
 ()  ascii ribbon campaign - against html e-mail 
 /\- against proprietary attachments