Kyocera Mita FS-1900 prints garbage

Bug #1512012 reported by Joachim Durchholz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Using the PPD from http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8.-downloadcenteritem-Single-License.downloadcenteritem.html?langLabel=de_de&actURL=/content/sites/kme/de/de/index/serviceworld/downloadcenter (the German one, not sure if that could make a difference).

Followed the instructions on https://wiki.ubuntu.com/DebuggingPrintingProblems.

Steps in "USB Printer" gave the following results:

2. lsmod | grep usb would give several modules (is usblp the right one? the page doesn't tell)
3. tailing the syslog would show me USB activity during plug and unplug.
6. lsusb output seems legit: Bus 001 Device 013: ID 0482:0004 Kyocera Corp.
8. Device id seems legit, usb_printerid /dev/usb/lp0 says ID:FS-1900;MFG:Kyocera;CMD:PCLXL,PostScript Emulation,PCL5E,PJL;MDL:FS-1900;CLS:PRINTER;DES:Kyocera Mita FS-1900;CID:HP Laserjet 4050 Series;
10. lpinfo -v has this to say about the printer: direct usb://Kyocera/FS-1900?serial=AAP2925070 (other non-network, direct printers listed are "direct hp" and "direct hpfax", could be a modem jack I never cared about, could be something emulated, no idea)

Printing the test page gives me two sheets of paper, the first mostly empty except for three lines each starting(?) with a single full stop character, and a second with these lines (note the initial blank on most line starts, could actually be multiple blanks):

 ERROR
 rangecheck
 OFFENDING COMMAND:
 filter
 STACK:
.
 563135
 --nostringval--
 --nostringval--
 5

The printer seems to be emitting a line with a full stop every 20 lines or so, the full stop in the message above is somehow connected to that.

From the DebuggingPrintingProblems page, I tried both usb-unidir-default and usb-no-reattach-default, with no discernible difference.

(Things were slightly complicated by the docking station being entirely unresponsibe on three of six USB ports. I don't know whether the ports of the drivers are at fault here, but I guess that's unrelated to CUPS.)

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cups 2.1.0-4ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CupsErrorLog:
 E [31/Oct/2015:21:36:32 +0100] [Job 29] Kann Daten nicht zum Drucker senden.
 E [31/Oct/2015:21:42:30 +0100] [Job 30] Kann Daten nicht zum Drucker senden.
CurrentDesktop: XFCE
Date: Sat Oct 31 21:45:05 2015
InstallationDate: Installed on 2015-08-24 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
Lpstat:
 device for Farblaser: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/
 device for FS-1900: usb://Kyocera/FS-1900?serial=AAP2925070
MachineType: Dell Inc. Precision M4600
Papersize: a4
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd', '/etc/cups/ppd/FS-1900.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied
 grep: /etc/cups/ppd/FS-1900.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: cups
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-28 (3 days ago)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 08V9YG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/26/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn08V9YG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :
Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :
Download full text (4.9 KiB)

Hm. Some more testing revealed an odd difference between the USB ports on the left and on the back side of my docking station.

The back ports work as one would expect: printer is recognized and gets registered when plugged in, and gets unregistered when unplugged; USB drive when plugged in gets recognized and has its directory shown in Thunar (XFCE here).
The left-side ports show inconsistent behaviour: The USB drive gets recognized and has its directory shown, but plugging in the printer does not provoke even a single new line in /var/log/syslog.

I'm wondering how such a difference is even possible.

For reference, here's the syslog from plugging the Kyocera to a back-side port:

Oct 31 22:19:17 jodel kernel: [12061.944337] usb 3-1.2.1: new full-speed USB device number 16 using ehci-pci
Oct 31 22:19:17 jodel kernel: [12062.038199] usb 3-1.2.1: New USB device found, idVendor=0482, idProduct=0004
Oct 31 22:19:17 jodel kernel: [12062.038202] usb 3-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 31 22:19:17 jodel kernel: [12062.038204] usb 3-1.2.1: Product: Kyocera Mita FS-1900
Oct 31 22:19:17 jodel kernel: [12062.038205] usb 3-1.2.1: Manufacturer: Kyocera Mita
Oct 31 22:19:17 jodel kernel: [12062.038214] usb 3-1.2.1: SerialNumber: AAP2925070
Oct 31 22:19:17 jodel kernel: [12062.039274] usblp 3-1.2.1:1.0: usblp0: USB Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x0482 pid 0x0004
Oct 31 22:19:17 jodel mtp-probe: checking bus 3, device 16: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2.1"
Oct 31 22:19:17 jodel mtp-probe: bus: 3, device: 16 was not an MTP device
Oct 31 22:19:17 jodel systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci0000:00-0000:00:1a.0-usb3-3\x2d1-3\x2d1.2-3\x2d1.2.1)...
Oct 31 22:19:17 jodel systemd[1]: Reached target Printer.
Oct 31 22:19:17 jodel udev-configure-printer[22613]: add /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2.1
Oct 31 22:19:17 jodel udev-configure-printer[22613]: device devpath is /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2.1
Oct 31 22:19:17 jodel udev-configure-printer[22613]: MFG:Kyocera MDL:FS-1900 SERN:- serial:AAP2925070
Oct 31 22:19:22 jodel kernel: [12067.091976] usblp0: removed
Oct 31 22:19:22 jodel kernel: [12067.094045] usblp 3-1.2.1:1.0: usblp0: USB Bidirectional printer dev 16 if 0 alt 0 proto 2 vid 0x0482 pid 0x0004
Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI contains USB serial number
Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI match: usb://Kyocera/FS-1900?serial=AAP2925070
Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI of detected printer: usb://Kyocera/FS-1900?serial=AAP2925070, normalized: kyocera fs 1900 serial aap2925070
Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI of print queue: dnssd://Xerox%20Phaser%206500DN%20(D6%3AA3%3AE5)._pdl-datastream._tcp.local/, normalized: dnssd xerox phaser 6500dn d6 a3 e5 pdl datastream tcp local
Oct 31 22:19:22 jodel udev-configure-printer[22613]: URI of print queue: usb://Kyocera/FS-1900?serial=AAP2925070, normalized: kyocera fs 1900 serial aap2925070
Oct 31 22:19:22 jodel udev-configure-printer[22613]: Queue ipp://localhost/printer...

Read more...

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

For the USB issues of te different USB ports of your docking station behaving differently, open a bug on the Linux kernel (Ubuntu package "linux").

Your printing problem can be a bug in the printer's PostScript interpreter, so please follow the instructions of section "PostScript (PDF) printer chokes on the PostScript (PDF) coming from Ubuntu" on https://wiki.ubuntu.com/DebuggingPrintingProblems.

As a workaround you can always try PPDs/drivers for PCL 6/XL or PCL 5e/c (see the "Generic" printers if you do not find anything appropriate in your printer's entry).

Please post your results here.

Changed in cups (Ubuntu):
status: New → Incomplete
Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

Okay, finding time to deal with this again.

Now I'm getting inconsistencies on the left-side port. Behaviour seems to vary according to previous history: Printing the test page first gave me the already-reported garbled output, switching off the printer and then switching it on again and retrying the printout gave me no activity on the printer and a hung print job.
So I suspect it's not the USB port that made the difference but previous history and dirty state somewhere.
What's the best way for get a full reset of all relevant state?

For reference, I'm attaching the cups error log, timestamps of my activities:
17:48:38 I started system-config-printer
17:49:38 I opened the Properties context menu entry on the printer
17:50:25 I let the Properties dialog print the test page (not the self-test page)
17:51:10 I confirmed the OK button on the "test page submitted" dialog box

Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :
Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

Ping?

Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

Not sure whether this is the right status after submitting all the relevant info, but "Incomplete" isn't right anymore.
Hopefully this thing will get a bit of love now...

Changed in cups (Ubuntu):
status: Incomplete → New
Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Hello Joachim,
Thank you for submitting this bug and reporting a problem with cups. You made this bug report some time ago and Ubuntu and cups have been updated since then.

Could you confirm that this is no longer a problem and that we can close the ticket?
If it is still a problem, are you still interested in finding a solution to this bug?
If you are, could you let us know and, in the current version, could you run the following (only once):
apport-collect 1512012
and upload the updated logs and and any other logs that are relevant for this particular issue.

Thank you again for helping make Ubuntu and cups better.
G

---
Ubuntu Bug Squad volunteer triager
https://wiki.ubuntu.com/BugSquad

Changed in cups (Ubuntu):
status: New → Incomplete
Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

Not going to collect that information again, don't want to waste time collecting information just to get ignored again.
So yeah you can close this, but not with a success please.

Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Thanks for the update, Joachim. I will close the report now.
Take care

G

Closed per reporter’s feedback.

Changed in cups (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Joachim Durchholz (jo-durchholz) wrote :

Hmf. "Invalid" adds insult to injury.

Revision history for this message
gf (gf-interlinks-deactivatedaccount) wrote :

Sorry Joachim. I only have the two options to close the ticket: fix released or invalid.
No offense meant.
Take care
:)
G

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.