Bug#718567: marked as done (cups: ipp14 backend cannot be set)
Your message dated Sat, 3 Aug 2013 09:33:05 +0200
with message-id <201308030933.06098.odyx@debian.org>
and subject line Re: Bug#718567: cups: ipp14 backend cannot be set
has caused the Debian Bug report #718567,
regarding cups: ipp14 backend cannot be set
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.)
--
718567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718567
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 1.5.3-5
Severity: normal
Dear Maintainer,
The problem is the same as told by others ipp backend does not work
with some printers after squeeze->wheezy upgrade (CUPS 1.4 -> 1.5).
I tried to follow Till's advices in order to use ipp14 backend
(see https://bugs.launchpad.net/ubuntu/+source/cups/+bug/945028 comment #56
and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712719 comment #44)
but command failed:
# lpadmin -p Canon -v ipp14://this.is.my.print.er/ipp/printer
lpadmin: Bad device-uri scheme "ipp14".
#
So I had to do the discouraged replacement of /usr/lib/cups/backend/ipp.
Gabor
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.10-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages cups depends on:
ii adduser 3.113+nmu3
ii bc 1.06.95-2
ii cups-client 1.5.3-5
ii cups-common 1.5.3-5
ii cups-filters 1.0.18-2.1
ii cups-ppdc 1.5.3-5
ii debconf [debconf-2.0] 1.5.49
ii dpkg 1.16.10
ii ghostscript 9.05~dfsg-6.3
ii libavahi-client3 0.6.31-2
ii libavahi-common3 0.6.31-2
ii libc-bin 2.13-38
ii libc6 2.13-38
ii libcups2 1.5.3-5
ii libcupscgi1 1.5.3-5
ii libcupsimage2 1.4.4-7+squeeze3
ii libcupsmime1 1.5.3-5
ii libcupsppdc1 1.5.3-5
ii libdbus-1-3 1.6.8-1+deb7u1
ii libgcc1 1:4.7.2-5
ii libgnutls26 2.12.20-7
ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u1
ii libkrb5-3 1.10.1+dfsg-5+deb7u1
ii libldap-2.4-2 2.4.31-1+nmu2
ii libpam0g 1.1.3-7.1
ii libpaper1 1.1.24+nmu2
ii libslp1 1.2.1-9
ii libstdc++6 4.7.2-5
ii libusb-1.0-0 2:1.0.11-1
ii lsb-base 4.1+Debian8+deb7u1
ii poppler-utils 0.18.4-6
ii procps 1:3.3.3-3
ii ssl-cert 1.0.32
Versions of packages cups recommends:
ii avahi-daemon 0.6.31-2
ii colord 0.1.21-1
ii foomatic-filters 4.0.17-1
ii ghostscript-cups 9.05~dfsg-6.3
ii printer-driver-gutenprint 5.2.9-1
Versions of packages cups suggests:
ii cups-bsd 1.5.3-5
pn cups-pdf <none>
ii foomatic-db 20120523-1
ii hplip 3.12.6-3.1
ii printer-driver-hpcups 3.12.6-3.1
ii smbclient 2:3.6.6-6
ii udev 175-7.2
-- debconf information:
* cupsys/raw-print: true
* cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd
--- End Message ---
--- Begin Message ---
Hi Gabor,
Le vendredi, 2 août 2013 13.19:13, Gabor Kiss a écrit :
> The problem is the same as told by others ipp backend does not work
> with some printers after squeeze->wheezy upgrade (CUPS 1.4 -> 1.5).
>
> I tried to follow Till's advices in order to use ipp14 backend
> (see https://bugs.launchpad.net/ubuntu/+source/cups/+bug/945028
> comment #56 and
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712719 comment #44)
> but command failed:
>
> # lpadmin -p Canon -v ipp14://this.is.my.print.er/ipp/printer
> lpadmin: Bad device-uri scheme "ipp14".
> #
>
> So I had to do the discouraged replacement of
> /usr/lib/cups/backend/ipp.
You first need to enable that backend in the dpkg configuration of cups:
# dpkg-reconfigure -plow cups
As you see; the ipp14 was not enabled in your setup:
> -- System Information:
> (…)
> -- debconf information:
> * cupsys/raw-print: true
> * cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd
Thereby closing this bug,
cheers
OdyX
--- End Message ---
Reply to: