Your message dated Tue, 20 Jun 2006 14:23:48 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#374532: foomatic-db-engine: Communication from
foomatic-configure to CUPS
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Subject: foomatic-db-engine: Communication from foomatic-configure to CUPS
Package: foomatic-db-engine
Version: 3.0.2-20060530-2
Severity: important
*** Please type your report below this line ***
I can not configure my printer Epson Stylus D88 with foomatic-configure.
debian:/home/david# foomatic-configure -n escp2-d88 -N 'Epson Stylus
D88' -c /dev/lp0 -d gutenprint\ -p Epson-Stylus_D88 --ppd
stp-escp2-D88.5.0.ppd.gz
The PPD file 'stp-escp2-D88.5.0.ppd.gz' does not exist or is readable.
foomatic-configure does not know the path, so we give the path:
debian:/home/david# foomatic-configure -n escp2-d88 -N 'Epson Stylus
D88' -c /dev/lp0 -d gutenprint -p Epson-Stylus_D88 --ppd
/usr/share/cups/model/gutenprint/5.0/en/stp-escp2-d88.5.0.ppd.gz
lpadmin: add-printer (set device) failed: client-error-not-possible
Could not set up/change the queue "escp2-d88"!
Error. Let's gunzip the file
debian:/home/david# gunzip
/usr/share/cups/model/gutenprint/5.0/en/stp-escp2-d88.5.0.ppd
debian:/home/david# foomatic-configure -n escp2-d88 -N 'Epson Stylus
D88' -c /dev/lp0 -d gutenprint -p Epson-Stylus_D88 --ppd
/usr/share/cups/model/gutenprint/5.0/en/stp-escp2-d88.5.0.ppd
lpadmin: add-printer (set device) failed: client-error-not-possible
Could not set up/change the queue "escp2-d88"!
gunzip has no effect.
debian:/home/david#
That means that the ppd-file was gzipped was not the problem.
There is an error message from lpadmin which belongs to the
package cupsys-client. It seems to me that foomatic-configure does not
call correctly lpadmin.
It is possible that there are errors in the file
/usr/share/cups/model/gutenprint/5.0/en/stp-escp2-d88.5.0.ppd.gz -
I do not understand how it is created and/or from which package it comes.
I have *not* installed package ijsgutenprint.
For installing foomatic-filters, foomatic-db, and foomatic-db-engine,
cupsys-driver-gutenprint, gutenprint-locales, and libgutenprint2
from the testing distribution, to satisfy dependencies I also had to
install following packages from the testing distribution:
coreutils
cpio
cramfsprogs
dash
initrd-tools
libacl1
libsepol1
libselinux1
util-linux
zlib1g
tzdata
libc6
libslang2
netcat
sed
lsb-base
libncurses5
libxml2
xml-core
libc6-dev
locales
util-linux-locales
zlib1g-dev
David Moerike, Friedrichshafen, Germany
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.16-386
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages foomatic-db-engine depends on:
ii bash 2.05b-26 The GNU Bourne Again SHell
ii foomatic-db 20060530-1 linuxprinting.org printer
support
ii foomatic-filters 3.0.2-20060530-1 linuxprinting.org printer
support
ii libc6 2.3.6-13 GNU C Library: Shared libraries
ii libxml2 2.6.24.dfsg-1 GNOME XML library
ii perl 5.8.4-8sarge4 Larry Wall's Practical
Extraction
ii wget 1.9.1-12 retrieves files from the web
ii zlib1g 1:1.2.3-11 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
The --ppd option is for use with true PostScript PPD files for
PostScript (or clone) printers; it is not at all useful with PPD files
supplied by either Gutenprint or Foomatic.
Omitting the --ppd option would (or at least should) have configured
the printer properly.
I have no idea why the CUPS web interface isn't working for you; my
guess is that the queue is stopped or paused for some reason, but
perusing the CUPS log files may give you some clues as to what is
going on.
Anyway, I'm closing this report since it's irrelevant to foomatic*.
Chris
--- End Message ---
