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

Bug#933879: marked as done (cups: Samsung CLP315 fails after update from Stretch to Buster)

Your message dated Mon, 5 Aug 2019 09:11:03 +0100
with message-id <05082019090546.96dc12b4ef5f@desktop.copernicus.org.uk>
and subject line Re: Bug#933879: cups: Samsung CLP315 fails after update from Stretch to Buster
has caused the Debian Bug report #933879,
regarding cups: Samsung CLP315 fails after update from Stretch to Buster
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.)


-- 
933879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933879
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Subject: cups: Samsung CLP315 fails after update from Stretch to Buster
Package: cups
Version: 2.2.10-6
Severity: normal



-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (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-6
ii  cups-common            2.2.10-6
ii  cups-core-drivers      2.2.10-6
ii  cups-daemon            2.2.10-6
ii  cups-filters           1.21.6-5
ii  cups-ppdc              2.2.10-6
ii  cups-server-common     2.2.10-6
ii  debconf [debconf-2.0]  1.5.71
ii  ghostscript            9.27~dfsg-2
ii  libavahi-client3       0.7-4+b1
ii  libavahi-common3       0.7-4+b1
ii  libc6                  2.28-10
ii  libcups2               2.2.10-6
ii  libcupsimage2          2.2.10-6
ii  libgcc1                1:8.3.0-6
ii  libstdc++6             8.3.0-6
ii  libusb-1.0-0           2:1.0.22-2
ii  poppler-utils          0.71.0-5
ii  procps                 2:3.3.15-2

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

Versions of packages cups suggests:
ii  cups-bsd                                   2.2.10-6
pn  foomatic-db-compressed-ppds | foomatic-db  <none>
pn  hplip                                      <none>
ii  printer-driver-cups-pdf [cups-pdf]         3.0.1-5
pn  printer-driver-hpcups                      <none>
ii  smbclient                                  2:4.9.5+dfsg-5
ii  udev                                       241-5

-- Configuration Files:
/etc/default/cups changed:


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


The printer worked with Stretch.
With Buster, the printer prints the following text for any printed page:

SPL-C ERROR - please use the proper driver
  POSITION : 0x0 (0)
  SYSTEM   : src/xl_image
  LINE     : 606
  VERSION  : SPL-C 5.35 11-20-2007
I have already tried within the cups web interface to change the printer setup and tried to delete the printer and then reassign connection and ppd file - but that did not make any change. 

Regards
Rudolf

--- End Message ---
--- Begin Message --- 
On Mon 05 Aug 2019 at 08:59:03 +0200, Rudolf Polzer wrote:

> > You will have a PPD for the printer in /etc/cups/ppd/. What does the
> > *NickName line in it say?
> 
> *NickName:      "Samsung CLP-310 Series (SPL-C)"

You appear to be using the Unified Linux Driver from Samsung. ULD is
not distributed or supported by Debian. Try the printer-driver-foo2zjs
package.

Cheers,

Brian.

--- End Message ---
Reply to: