Bug#370944: marked as done (cupsys: Upgrade to 1.2 broke printing on local parallel GDI printer)
Your message dated Sun, 23 Jul 2006 20:10:21 +0900
with message-id <20060723111021.426151A7981@mail.topstudio.co.jp>
and subject line cupsys: Upgrade to 1.2 broke printing on local parallel GDI printer
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 ---
- To: Debian Bug Tracking System <firstname.lastname@example.org>
- Subject: cupsys: Upgrade to 1.2 broke printing on local parallel GDI printer
- From: Shai Berger <email@example.com>
- Date: Wed, 07 Jun 2006 03:51:30 +0300
- Message-id: <firstname.lastname@example.org>
Since the upgrade to cupsys 1.2, I cannot print. lpq reports
the printer as "not ready", and the cupsys web interface
shows it as:
Xerox (Default Printer) "/usr/lib/cups/backend/parallel failed"
Description: GENERIC GDI Printer gdi
Make and Model: Generic GDI Printer Foomatic/gdi
Printer State: stopped, accepting jobs, published.
Device URI: parallel:/dev/lp0
Starting the printer reports success and makes it "idle"; printing
anything fails and sends it back to "stopped".
With 1.2.1-1, I could get the "/usr/lib/cups/backend/parallel failed"
message to change to something like "/dev/lp0: permission denied",
but I can't seem to reproduce this now with 1.2.1-2. This message
made no sense to me, as cupsd runs as root, and so has permissions
to read and write lp0.
Trying to print a test page from the web interface gives me a
Quota limit reached.
message, which makes no sense, as I've never set any quotas.
I've checked that the printer and physical connection to it are
ok by (booting into and) printing from a different OS.
I suspect some of my woes are related to upstream bug #1738
it seems like there is more at stake.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages cupsys depends on:
ii adduser 3.87 Add and remove users and groups
ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy
ii gs-esp 8.15.1.dfsg.1-2 The Ghostscript PostScript interpr
ii libacl1 2.2.37-1 Access control list shared library
ii libc6 2.3.6-13 GNU C Library: Shared libraries
ii libcupsimage2 1.2.1-2 Common UNIX Printing System(tm) -
ii libcupsys2 1.2.1-2 Common UNIX Printing System(tm) -
ii libdbus-1-2 0.61-6 simple interprocess messaging syst
ii libgnutls13 1.3.5-1.1 the GNU TLS library - runtime libr
ii libldap2 2.1.30-13 OpenLDAP libraries
ii libpam0g 0.79-3.1 Pluggable Authentication Modules l
ii libpaper1 1.1.17 Library for handling paper charact
ii libslp1 1.2.1-5 OpenSLP libraries
ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip
ii patch 2.5.9-4 Apply a diff file to an original
ii perl-modules 5.8.8-5 Core Perl modules
ii procps 1:3.2.6-2.2 /proc file system utilities
ii xpdf-utils [poppler-util 3.01-8 Portable Document Format (PDF) sui
ii zlib1g 1:1.2.3-11 compression library - runtime
Versions of packages cupsys recommends:
ii cupsys-client 1.2.1-2 Common UNIX Printing System(tm) -
ii foomatic-filters 3.0.2-20060530-1 linuxprinting.org printer support
ii smbclient 3.0.22-1 a LanManager-like simple client fo
-- debconf information:
* cupsys/raw-print: true
* cupsys/browse: true
* cupsys/ports: 631
* cupsys/backend: ipp, lpd, parallel, socket, usb
--- End Message ---
--- Begin Message ---
- To: email@example.com
- Subject: Re: cupsys: Upgrade to 1.2 broke printing on local parallel GDI printer
- From: Kenshi Muto <firstname.lastname@example.org>
- Date: Sun, 23 Jul 2006 20:10:21 +0900
- Message-id: <20060723111021.426151A7981@mail.topstudio.co.jp>
I think this bug is solved by 1.2.1-4.
--- End Message ---