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

Bug#404763: marked as done (cupsys-bsd: lprm asks for password, won't accept, won't kill)

Your message dated Fri, 17 May 2013 23:18:57 +0300 (EEST)
with message-id <20130517201857.0702FC1A10@sid.nuvreauspam>
and subject line Bug #404763 filed against cupsys (or a related package)
has caused the Debian Bug report #404763,
regarding cupsys-bsd: lprm asks for password, won't accept, won't kill
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 owner@bugs.debian.org
immediately.)


-- 
404763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404763
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupsys-bsd
Version: 1.2.7-1
Severity: normal

lprm asks for a password.  Asks for the wrong password (whitis vs root)
and doesn't accept either password.   Can't control-c, either.

ml1710 is ready and printing
Rank    Owner   Job     File(s)                         Total Size
active  root    71                                      200704 bytes
1st     root    72                                      200704 bytes
2nd     root    73                                      200704 bytes
3rd     root    74      (stdin)                         28672 bytes
4th     root    75      (stdin)                         28672 bytes
You have new mail in /var/mail/whitis
whitis@cervantes:~$ lprm -
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost?
Password for whitis on localhost? Terminated   (killall lprm)

I just upgraded from unstable to stable during the last 24 hours using
dist-upgrade.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages cupsys-bsd depends on:
ii  cupsys-client                1.2.7-1     Common UNIX Printing System(tm) - 
ii  cupsys-common                1.2.7-1     Common UNIX Printing System(tm) - 
ii  debconf                      1.5.11      Debian configuration management sy
ii  libc6                        2.3.6.ds1-9 GNU C Library: Shared libraries
ii  libcupsys2                   1.2.7-1     Common UNIX Printing System(tm) - 
ii  libgnutls13                  1.4.4-3     the GNU TLS library - runtime libr
ii  netbase                      4.27        Basic TCP/IP networking system

cupsys-bsd recommends no packages.

-- debconf information:
* cupsys-bsd/setuplpd: false

--- End Message ---
--- Begin Message --- 
Version: 1.4.4-1

Hello,

Some (long) time ago you filed this bug against cupsys or a related 
package. In the meantime the cupsys package has been renamed to cups and 
this bug was "lost". Since it is quite old now it is being closed.

If the issue you encountered is still present in recent cups packages 
(as released with Debian 7.0 wheezy for example) the CUPS maintainers 
would very much appreciate a fresh report using

    reportbug <package>

(you should also mention the number of this bug if you think it contains 
valuable information).

Please note that further information sent to this bug is likely to 
remain unread, because the bug is currently not assigned to any existing 
package.


Thank you for taking time to report bugs found in Debian packages.

Kind regards,
Andrei (with no relation to CUPS maintenance)

--- End Message ---
Reply to: