Your message dated Sat, 6 Sep 2008 19:23:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#367479: [Debian QA] please review your old bug reports
against CUPS
has caused the Debian Bug report #367479,
regarding cupsys: CUPS 1.2 experimental package does not permit administration
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 [EMAIL PROTECTED]
immediately.)
--
367479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367479
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: cupsys
Version: 1.1.99.rc2-0exp1
Severity: important
Running the following commands:
$ cupsenable epl-6200
Password for rleigh on localhost?
$ sudo cupsenable epl-6200
results in these log messages:
[16/May/2006:11:07:46 +0100] Resume-Printer: Unauthorized
E [16/May/2006:11:07:50 +0100] PID 14768 (/usr/lib/cups/backend/usb) stopped
with status 1!
E [16/May/2006:11:07:50 +0100] [Job 252] Unable to open USB device
"usb:/dev/usb/lp1": Success
E [16/May/2006:11:08:03 +0100] Resume-Printer: Unauthorized
E [16/May/2006:11:08:03 +0100] PID 14771 (/usr/lib/cups/backend/usb) stopped
with status 1!
E [16/May/2006:11:08:03 +0100] [Job 252] Unable to open USB device
"usb:/dev/usb/lp1": Success
It's not clear why it's not authorised. User "rleigh" is in the
"lpadmin" group, and root is root. The cupsd.conf hasn't been touched
since installation.
The "Unable to open USB device "usb:/dev/usb/lp1": Success" error is
also rather strange. The device exists, and the printer is switched
on...
BTW, one other consideration is that the web interface (at least for the
1.1.x versions) requires logging on as root by default. Since it's
common to disable the root password and use sudo only (for security), it
would be nice if the packaging could cater for this in some way, e.g.
asking which user you wish to use as the printing administrator, and
adding them to the lpadmin group (or at least documenting this clearly),
if using the lpadmin group is the correct way to do things.
Regards,
Roger
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.9
Locale: LANG=en_GB.UTF8, LC_CTYPE=en_GB.UTF8 (charmap=UTF-8)
Versions of packages cupsys depends on:
ii adduser 3.87 Add and remove users and groups
ii cdebconf [debconf-2.0] 0.101 Debian Configuration Management Sy
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 libc6 2.3.6-7 GNU C Library: Shared libraries
ii libcupsimage2 1.1.99.rc2-0exp1 Common UNIX Printing System(tm) -
ii libcupsys2 1.1.99.rc2-0exp1 Common UNIX Printing System(tm) -
ii libdbus-1-2 0.61-5 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.16 Library for handling paper charact
ii libslp1 1.2.1-5 OpenSLP libraries
ii lsb-base 3.1-5 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-4 Core Perl modules
ii poppler-utils [xpdf-uti 0.4.5-4 PDF utilitites (based on libpopple
ii procps 1:3.2.6-2.2 /proc file system utilities
ii zlib1g 1:1.2.3-11 compression library - runtime
Versions of packages cupsys recommends:
ii cupsys-client 1.1.99.rc2-0exp1 Common UNIX Printing System(tm) -
ii foomatic-filters 3.0.2-20060318-2 linuxprinting.org printer support
pn smbclient <none> (no description available)
-- debconf information:
cupsys/raw-print: true
* cupsys/ports: 631
cupsys/backend: ipp, lpd, parallel, socket, usb
cupsys/portserror:
* cupsys/browse: true
--- End Message ---
--- Begin Message ---
Version: 1.3.8-1
Roger Leigh [2007-07-15 12:42 +0100]:
> % id
> uid=1000(rleigh) gid=1000(rleigh) groups=...,106(lpadmin),...
>
> % cupsenable epl-6200
> [..]
> I [15/Jul/2007:12:37:30 +0100] Printer "epl-6200" started by "root".
> D [15/Jul/2007:12:37:30 +0100] cupsdProcessIPPRequest: 7 status_code=0
> (successful-ok)
> D [15/Jul/2007:12:37:30 +0100] cupsdCloseClient: 7
>
> % cupsdisable epl-6200
> [...]
> I [15/Jul/2007:12:37:46 +0100] Printer "epl-6200" stopped by "root".
> D [15/Jul/2007:12:37:46 +0100] cupsdProcessIPPRequest: 7 status_code=0
> (successful-ok)
This looks perfectly fine.
> I still get the Pause-Printer errors, but it then continues to stop
> the printer
That's normal, it always tries to connect unauthorized first, and then
gets authorization and tries again. Not sure why cups does it that
way, but that happens everywhere.
I close the bug. Thanks for testing again!
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
