Package: foomatic-db-engine
Version: 3.0.2-20050720-1
Followup-For: Bug #261662

I did a dist-upgrade the other day and ever since printing has been
broken.  Running foomatic-configure to recover, I see:

 foomatic-configure -n lp -N 'Lexmark Z52' -L infidel -c /dev/lp0 -p \
                     gimp-print -d gimp-print-ijs -s lpd
Cannot read file /usr/share/foomatic/db/source/printer/gimp-print.xml!
Cannot read file /usr/share/foomatic/db/source/printer/gimp-print.xml!
Printer file /usr/share/foomatic/db/source/printer/gimp-print.xml \
            corrupted, missing, or not readable!
Could not run "foomatic-combo-xml"/"foomatic-perl-data"! at \
            /usr/share/perl5/Foomatic/DB.pm line 528.


-- System Information:
Debian Release: testing
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-386
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_CA)

Versions of packages foomatic-db-engine depends on:
ii  bash                    3.0-16           The GNU Bourne Again SHell
ii  curl                    7.14.0-5         Get a file from an HTTP, HTTPS, FT
ii  foomatic-db             20050720-1       linuxprinting.org printer support 
ii  foomatic-filters        3.0.2-20050720-1 linuxprinting.org printer support 
ii  libc6                   2.3.5-6          GNU C Library: Shared libraries an
ii  libxml2                 2.6.22-1         GNOME XML library
ii  perl                    5.8.7-6          Larry Wall's Practical Extraction 
ii  wget                    1.10.1-1         retrieves files from the web
ii  zlib1g                  1:1.2.3-4        compression library - runtime

Versions of packages foomatic-db-engine recommends:
ii  netcat                        1.10-27    TCP/IP swiss army knife

-- no debconf information

-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)               http://www.spots.ab.ca/~keeling 
- -


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to