Bug#370409: cupsys: When modifying a printer, the UI forgets the device URI.
Package: cupsys
Version: 1.2.1-1
Severity: normal
Whenever I modify a printer (ie, when the PPD file changes) the device
URI defaults to "socket" (I'm using a HP with a JetDirect card in it).
When means I then have to go back to the printer overview page and
cut'n'paste the device URI. It seems to me that the modify page should
have the current URI in the input box.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.6-cerberus
Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1) (ignored: LC_ALL set to en_NZ)
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-1 Common UNIX Printing System(tm) -
ii libcupsys2 1.2.1-1 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.18 Library for handling paper charact
ii libslp1 1.2.1-5 OpenSLP libraries
ii lsb-base 3.1-9 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-1 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 excluded
Reply to: