Red Hat Bugzilla – Bug 1308688
Selected wrong driver for Samsung CLP-310
Last modified: 2016-12-20 13:44:59 EST
Created attachment 1127391 [details]
CUPS troubleshoot log
Description of problem:
I did a fresh install of Fedora 23 and attempted to print a test document to my Samsung CLP-310 printer, connected via USB. The printer whirs to life and Cups claims success, but nothing prints.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Clean install of Fedora 23
2. Print test page
Printer hangs with Printer State status of "Idle - Sending data to printer"
Printed test page.
This exact same hardware was working under Fedora 20, but it got EOL'ed and I figured upgrading to 23 would be fine. Apparently not.
I did the CUPS troubleshooting tool and it said there was nothing it could figure out. I've attached the status page it provided.
Created attachment 1127392 [details]
CUPS journalctl activity for printing the test page
journalctl -u cups --since "2016-02-15 13:10:00"
(In reply to Justin Moore from comment #0)
> Created attachment 1127391 [details] (CUPS troubleshoot log)
> 'printer-make-and-model': 'Samsung CLP-350 Series PS'
Problem is that the printer has been configured to use CLP-350 drivers, even there are drivers for CLP-310 in splix and foo2qpdl packages.
You can install splix and/or foo2qpdl packages and then change the driver/Model
# python3 -c "import cupshelpers; cupshelpers.xmldriverprefs.test(xml_path='/etc/cupshelpers/',deviceid='MFG:Samsung;CMD:SPLC;MDL:CLP-310 Series;CLS:PRINTER;STATUS:IDLE;')"
# rpm -q --provides splix
# rpm -q --provides foo2qpdl
I installed the splix and foo2qpdl packages and updated the driver to the Samsung CLP-315 model. Printing now works.
Leaving this open for now to see if there's any fixes to be applied to the install/detection process to let other CLP-31 owners know what to do in this situation.
Upstream pull request:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I would like to report the same bug for a slightly different printer and with a workaround:
1. On a clean install if I use the printer manager tool to install my CLX-3175 printer, the printer appears to install ok, but prints nothing.
2. If the foo2qpdl package has been installed before installing the printer through the printer manager tool then I get a working printer.
So: whatever algorithm is used by the printer manager tool to install the printer is wrong, and the resulting failed printer is very difficult to diagnose -- using system-config-printer as suggested by one Fedora help page basically produced the response "sorry, can't help".
On the other hand, an easy workaround is to install foo2qpdl first ... if only I'd known!
P.S. The colour profile for this printer is *dreadful*, but guess that's a totally unrelated issue!
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.
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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.