Red Hat Bugzilla – Bug 811642
Kyocera FS-1118MFP print very slow with recommended driver
Last modified: 2013-08-01 08:44:20 EDT
Description of problem:
Kyocera FS-1118MFP prints very slow with recommended driver.
Every page printed with driver "Kyocera FS-1118MFP" above 3 minutes (attached example file)!
With driver "Kyocera FS-1118MFP - CUPS Gutenprint v5.2.7" this problem is absent.
All three attached pages appear instantly in a few seconds.
But with driver "Kyocera FS-1118MFP - CUPS Gutenprint v5.2.7" I every time for print come to printer for choose paper. See bug https://bugzilla.redhat.com/show_bug.cgi?id=788472
Therefore it is necessary either to "Kyocera FS-1118MFP" printed well, as fast as the "Kyocera FS-1118MFP - CUPS Gutenprint v5.2.7" or to nebylo problems with the choice of paper by using "Kyocera FS-1118MFP - CUPS Gutenprint v5.2.7 ".
Created attachment 576810 [details]
example file which printed with Evince
Can you attach an output from "Printing troubleshooter" when using the "Kyocera FS-1118MFP" driver ?
Created attachment 577232 [details]
Created attachment 577233 [details]
troubleshoot-Kyocera FS-1118MFP - CUPS Gutenprint v5.2.7
It looks like the printer stops accepting data, possibly because it is processing the job.
You could capture the TCP traffic so we could find out if there is some other reason for the stall:
tcpdump -n -U0 -w jetdirect.pcap host 10.10.8.190
Run that command as root, then submit a print job. Once the job has completed, press control-C to stop the tcpdump command, and finally attach jetdirect.pcap to this bug report using the "Add an attachment" link further up this page.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.