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

Bug#919195: marked as done (cups: gutenprint driver nmo longer workin after upgrade)

Your message dated Thu, 14 Nov 2019 19:54:13 +0000
with message-id <14112019194811.8305c8bce151@desktop.copernicus.org.uk>
and subject line Re: Bug#919195: cups: gutenprint driver nmo longer workin after upgrade
has caused the Debian Bug report #919195,
regarding cups: gutenprint driver nmo longer workin after upgrade
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.)


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

Hello,

I upgraded cups from stable to testing and I am no longer able to print.

The driver used with stable was something like 'HP LaserJet 6MP
CUPS+gutenprint v5.2' and after upgrade this driver is no longer
available. There is something like 'HP LaserJet 6MP CUPS+gutenprint v5.3.2'
(just different version number in the string) but it needs to be
selected manually after upgrade. During upgrade I was required to type
root password to do some upgrade but in spite of that the driver is not
upgraded.

Please consider performing upgrade to current gutenprint driver as par
of this postint upgrade process.

Thanks

Michal


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
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.2.10-3
ii  cups-common            2.2.10-3
ii  cups-core-drivers      2.2.10-3
ii  cups-daemon            2.2.10-3
ii  cups-filters           1.21.6-2
ii  cups-ppdc              2.2.10-3
ii  cups-server-common     2.2.10-3
ii  debconf [debconf-2.0]  1.5.69
ii  ghostscript            9.26~dfsg-2
ii  libavahi-client3       0.7-4+b1
ii  libavahi-common3       0.7-4+b1
ii  libc6                  2.28-2
ii  libcups2               2.2.10-3
ii  libcupsimage2          2.2.10-3
ii  libgcc1                1:8.2.0-13
ii  libstdc++6             8.2.0-13
ii  libusb-1.0-0           2:1.0.22-2
ii  poppler-utils          0.69.0-2
ii  procps                 2:3.3.15-2

Versions of packages cups recommends:
ii  avahi-daemon                     0.7-4+b1
ii  colord                           1.4.3-3+b1
ii  cups-filters [ghostscript-cups]  1.21.6-2
ii  printer-driver-gutenprint        5.3.1-6

Versions of packages cups suggests:
ii  cups-bsd                                   2.2.10-3
pn  cups-pdf                                   <none>
pn  foomatic-db-compressed-ppds | foomatic-db  <none>
pn  hplip                                      <none>
pn  printer-driver-hpcups                      <none>
pn  smbclient                                  <none>
ii  udev                                       240-2

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

--- End Message ---
--- Begin Message --- 
Odyx asked:

 > This should be fixed by printer-driver-gutenprint 5.3.1-7 (#790045 / #918726);
 > could you confirm this?

In the light of the time that has elapsed I am going to assume the
issue on an unstable installation has didsappeared. Otherwise, a new
report could be submitted.

Regards,

Brian.

--- End Message ---
Reply to: