Your message dated Sun, 6 Mar 2016 22:32:42 +0000
with message-id <[email protected]>
and subject line Re: Bug#642508: cups-client: lpstat without options segfaults
has caused the Debian Bug report #642508,
regarding cups-client: lpstat without options segfaults
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 [email protected]
immediately.)


-- 
642508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642508
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cups-client
Version: 1.5.0-7
Severity: normal

Dear Maintainer,

running lpstat without any options produces a segfault on my system
Workaround is to add an option, e.g., lpstat -a.
This happens with libcupsimage2/libcups2/cups-common from stable (1.5.0-5)
as well with the version stated below, so I'd assume it might be a bug in the 
lpstat code itself


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cups-client depends on:
ii  adduser        3.113  
ii  cups-common    1.5.0-7
ii  libc6          2.13-18
ii  libcups2       1.5.0-7
ii  libcupsimage2  1.5.0-7

Versions of packages cups-client recommends:
ii  smbclient  2:3.5.11~dfsg-1

Versions of packages cups-client suggests:
pn  cups      1.5.0-5
pn  cups-bsd  <none> 
pn  xpp       <none> 

-- no debconf information



--- End Message ---
--- Begin Message ---
I still cannot reproduce this bug on cups 2.1.3-3, Closing.

Regards,

Brian.

--- End Message ---

Reply via email to