[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#373899: marked as done (cupsys: USB backend cannot access /dev/usb/lp0)

Your message dated Fri, 28 Jul 2006 09:39:46 +0900
with message-id <20060728003946.C438E1A7A90@mail.topstudio.co.jp>
and subject line Bug#373899: cupsys: USB backend cannot access /dev/usb/lp0
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 --- 
Package: cupsys
Version: 1.2.1-2
Severity: grave


When the USB backend process is spawned, its UID is set to 7 (lp), but
the GID remains 0 (I've checked in /proc/NNNN/status). This makes CUPS
incompatible with the default configuration of udev, which sets for
/dev/usb/lp[0-9] owner root, group lp, and mode 660.

The backend process should be spawned with GID 7 (lp) as well as UID 7 (lp).

Severity justification: local printers which use parallel, serial, and
usb backends, are unusable without manual reconfiguration of udev.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (90, 'experimental'), (90, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

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-4         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-show failed

--- End Message ---
--- Begin Message --- 
Version: 1.2.1-3
thanks

At Fri, 16 Jun 2006 15:01:01 +0700,
Alexey Feldgendler wrote:
> Package: cupsys
> Version: 1.2.1-2
> Severity: grave
> 
> When the USB backend process is spawned, its UID is set to 7 (lp), but
> the GID remains 0 (I've checked in /proc/NNNN/status). This makes CUPS
> incompatible with the default configuration of udev, which sets for
> /dev/usb/lp[0-9] owner root, group lp, and mode 660.
> 
> The backend process should be spawned with GID 7 (lp) as well as UID 7 (lp).

Original this problem seems be already solved, at least since 1.2.1-3.
Other additional reports are different issues and look already be
submitted as another Bug#.

Thanks,
-- 
Kenshi Muto
kmuto@debian.org

--- End Message ---
Reply to: