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

Bug#712719: marked as done (cups: CUPS printing broken in Wheezy (Unable to get printer status))



Your message dated Tue, 26 Apr 2016 18:23:30 +0100
with message-id <26042016181943.477b6477c03a@desktop.copernicus.demon.co.uk>
and subject line Re: Bug#712719: cups: CUPS printing broken in Wheezy (Unable to get printer status)
has caused the Debian Bug report #712719,
regarding cups: CUPS printing broken in Wheezy (Unable to get printer status)
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.)


-- 
712719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712719
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 1.5.3-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
Squeeze->Wheezy upgrade. Done on 2 machines - both have the same problem now
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Recreated printer, reinstalled CUPS, connected locally (instead over ipp)
   * What was the outcome of this action?
Nope.
Get-Printer-Attributes returned server-error-internal-error
Unable to get printer status.
   * What outcome did you expect instead?
That I'll be able to print.



-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cups depends on:
ii  adduser                3.113+nmu3
ii  bc                     1.06.95-2
ii  cups-client            1.5.3-5
ii  cups-common            1.5.3-5
ii  cups-filters           1.0.18-2.1
ii  cups-ppdc              1.5.3-5
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg                   1.16.10
ii  ghostscript            9.05~dfsg-6.3
ii  libavahi-client3       0.6.31-2
ii  libavahi-common3       0.6.31-2
ii  libc-bin               2.13-38
ii  libc6                  2.13-38
ii  libcups2               1.5.3-5
ii  libcupscgi1            1.5.3-5
ii  libcupsimage2          1.5.3-5
ii  libcupsmime1           1.5.3-5
ii  libcupsppdc1           1.5.3-5
ii  libdbus-1-3            1.6.8-1+deb7u1
ii  libgcc1                1:4.7.2-5
ii  libgnutls26            2.12.20-7
ii  libgssapi-krb5-2       1.10.1+dfsg-5+deb7u1
ii  libkrb5-3              1.10.1+dfsg-5+deb7u1
ii  libldap-2.4-2          2.4.31-1+nmu2
ii  libpam0g               1.1.3-7.1
ii  libpaper1              1.1.24+nmu2
ii  libslp1                1.2.1-9
ii  libstdc++6             4.7.2-5
ii  libusb-1.0-0           2:1.0.11-1
ii  lsb-base               4.1+Debian8+deb7u1
ii  poppler-utils          0.18.4-6
ii  procps                 1:3.3.3-3
ii  ssl-cert               1.0.32

Versions of packages cups recommends:
ii  avahi-daemon               0.6.31-2
ii  colord                     0.1.21-1
ii  foomatic-filters           4.0.17-1
ii  ghostscript-cups           9.05~dfsg-6.3
ii  printer-driver-gutenprint  5.2.9-1

Versions of packages cups suggests:
pn  cups-bsd               <none>
ii  cups-pdf               2.6.1-6
ii  foomatic-db            20120523-1
pn  hplip                  <none>
ii  printer-driver-hpcups  3.12.6-3.1
ii  smbclient              2:3.6.6-6
ii  udev                   175-7.2

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

--- End Message ---
--- Begin Message ---
On Tue 18 Jun 2013 at 21:05:56 +0200, Adrian wrote:

>    * What led up to the situation?
> Squeeze->Wheezy upgrade. Done on 2 machines - both have the same problem now
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> Recreated printer, reinstalled CUPS, connected locally (instead over ipp)
>    * What was the outcome of this action?
> Nope.
> Get-Printer-Attributes returned server-error-internal-error
> Unable to get printer status.
>    * What outcome did you expect instead?
> That I'll be able to print.

Hello Adrian, thank you for your report and supporting information. 

With the ending of support for Wheezy this report is being closed. It
would also appear the issue was cleared up in a satisfactory manner.

Regards,

Brian.

--- End Message ---

Reply to: