Package: lprng Version: 3.8.28-2 Severity: normal
Hello. A while ago, I reported a memory leak about the time that some changes were done to the main package by Patrick. You thought that they would solve the memory leak problem. And they did seem to. Today I was printing some SVG stuff from Inkscape, and lprng started chewing up memory again. Not quite as fast as the last time, but after a couple of hours things were getting quite sluggish again. Do you have a plan for finding out where this memory is leaking? I'm going to need to print those SVG files again in the near future, so I can set things up with lprng quite easily. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.27 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages lprng depends on: ii debconf 1.4.46 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcomerr2 1.36release-1 common error description library ii libkrb53 1.3.6-1 MIT Kerberos runtime libraries ii libssl0.9.7 0.9.7e-3 SSL shared libraries -- debconf information: lprng/twolpd_perms: lprng/twolpd_conf: * lprng/setuid_tools: true * lprng/start_lpd: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
