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

Bug#942190: marked as done (cups: Memory leak for WIFI enabled printer.)

Your message dated Mon, 10 Jan 2022 13:44:07 +0000
with message-id <10012022134209.94393c1ae07b@desktop.copernicus.org.uk>
and subject line Re: Bug#942190: cups: Memory leak for WIFI enabled printer.
has caused the Debian Bug report #942190,
regarding cups: Memory leak for WIFI enabled printer.
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.)


-- 
942190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942190
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups
Version: 2.3.0-5
Severity: normal

I have HP LaserJet 1102W which I use through WIFI network. Over time cupsd
starts leaking memory and within few hours goes to 1GB sometimes.

Printer requires HP's LIP service and drivers to work.

I have also noticed that when printer is interrupted in half-print, even if I
rester printing service memory will leak. Since I have never reported cups
related issues submitting additional information would require some level of
guidance.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups depends on:
ii  cups-client            2.3.0-5
ii  cups-common            2.3.0-5
ii  cups-core-drivers      2.3.0-5
ii  cups-daemon            2.3.0-5
ii  cups-filters           1.25.6-1
ii  cups-ppdc              2.3.0-5
ii  cups-server-common     2.3.0-5
ii  debconf [debconf-2.0]  1.5.73
ii  ghostscript            9.27~dfsg-3.1
ii  libavahi-client3       0.7-4+b1
ii  libavahi-common3       0.7-4+b1
ii  libc6                  2.29-2
ii  libcups2               2.3.0-5
ii  libgcc1                1:9.2.1-8
ii  libstdc++6             9.2.1-8
ii  libusb-1.0-0           2:1.0.23-1
ii  poppler-utils          0.71.0-6
ii  procps                 2:3.3.15-2+b1

Versions of packages cups recommends:
ii  avahi-daemon                     0.7-4+b1
ii  colord                           1.4.3-4
ii  cups-filters [ghostscript-cups]  1.25.6-1
ii  printer-driver-gutenprint        5.3.3-2

Versions of packages cups suggests:
ii  cups-bsd                                   2.3.0-5
pn  cups-pdf                                   <none>
ii  foomatic-db-compressed-ppds [foomatic-db]  20190913-1
ii  hplip                                      3.19.8+dfsg0-7
ii  printer-driver-hpcups                      3.19.8+dfsg0-7
pn  smbclient                                  <none>
ii  udev                                       242-7

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: lpd, socket, usb, snmp, dnssd

--- End Message ---
--- Begin Message --- 
On Fri 11 Oct 2019 at 22:00:40 +0200, Mladen Mijatov wrote:

> Package: cups
> Version: 2.3.0-5
> Severity: normal
>
> I have HP LaserJet 1102W which I use through WIFI network. Over time cupsd
> starts leaking memory and within few hours goes to 1GB sometimes.
>
> Printer requires HP's LIP service and drivers to work.
>
> I have also noticed that when printer is interrupted in half-print, even if I
> rester printing service memory will leak. Since I have never reported cups
> related issues submitting additional information would require some level of
> guidance.

Dear Debian User,

Further information on your issue was requested some time ago but there
hasn't been any response from you. Use of our limited, volunteer
supported resources is best served by not keeping open inactive bugs any
longer than desirable, especially in cases where the package concerned
is older than the current stable Debian version. Consequently, the
report is now being closed.

Regards,

Brian.

--- End Message ---
Reply to: