Bug#374933: marked as done (/usr/bin/lpstat: 'lpstat -l -d -p -v' leads to infinite loop with more than one printer instance)
Your message dated Sat, 6 Sep 2008 22:24:48 -0500
with message-id <e2e0e3d30809062024k1e0e6c8br46210970dee14bf8@mail.gmail.com>
and subject line Re: Bug#374933: /usr/bin/lpstat: 'lpstat -l -d -p -v' leads to infinite loop with more than one printer instance
has caused the Debian Bug report #374933,
regarding /usr/bin/lpstat: 'lpstat -l -d -p -v' leads to infinite loop with more than one printer instance
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.)
--
374933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374933
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: /usr/bin/lpstat: 'lpstat -l -d -p -v' leads to infinite loop with more than one printer instance
- From: Chris Lawrence <lawrencc@debian.org>
- Date: Thu, 22 Jun 2006 01:04:12 -0400
- Message-id: <20060622050412.24508.76775.reportbug@campbell.lordsutch.dyndns.org>
Package: cupsys-client
Version: 1.2.1-2
Severity: important
File: /usr/bin/lpstat
On my system (and presumably others), the command line
> lpstat -l -d -p -v
or
> lpstat -l -d -p
leads to an infinite loop that will consume all system memory and CPU.
It seems to get stuck when I have more than one extra instance of the
printer in my .lpoptions file (e.g. hl5170dn/bond, hl5170dn/duplex).
When I only have zero or one instances, there is no problem.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.20
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages cupsys-client depends on:
ii adduser 3.87 Add and remove users and groups
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libcupsys2 1.2.1-2 Common UNIX Printing System(tm) -
ii libgnutls13 1.4.0-2 the GNU TLS library - runtime libr
ii zlib1g 1:1.2.3-11 compression library - runtime
Versions of packages cupsys-client recommends:
ii cupsys-bsd 1.2.1-2 Common UNIX Printing System(tm) -
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.3.8-1lenny1
On Sat, Sep 6, 2008 at 12:30 PM, Martin Pitt <mpitt@debian.org> wrote:
> tag 374933 moreinfo
> thanks
>
> Hi Chris,
>
> Chris Lawrence [2006-06-22 1:04 -0400]:
>> On my system (and presumably others), the command line
>> > lpstat -l -d -p -v
>> or
>> > lpstat -l -d -p
>>
>> leads to an infinite loop that will consume all system memory and CPU.
>>
>> It seems to get stuck when I have more than one extra instance of the
>> printer in my .lpoptions file (e.g. hl5170dn/bond, hl5170dn/duplex).
>> When I only have zero or one instances, there is no problem.
>
> Do you still have the problem in recent Lenny/testing or unstable
> versions?
>
> Can you please attach your ~/.lpoptions and /etc/cups/printers.conf
> files, so that I can reproduce the issue?
The problem appears to be fixed, at least in cups-client
1.3.8-1lenny1. Thanks for the followup.
Chris
--- End Message ---
Reply to: