Samsung ML-1740: "gdi" driver is used by default and not SpliX
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: splix
Dear Ubuntu folks:
Thank you for packaging all this good software for Ubuntu!
My Samsung ML-1740 isn't working very well with my new Natty computer. Inspecting the configuration, I see that it is using the GDI driver which is reputed to be problematic on openprinting.org. The splix driver is recommended instead. I've always had excellent performance from using the splix driver with this printer in the past. So, for starters the default configuration of Ubuntu should probably be changed to use the Splix driver for this printer.
But in any case, I can't seem to find the Splix driver PPD within Ubuntu. The "splix" package is installed, but there are no PPD files in /usr/share/
I know that in previous distributions of Ubuntu the "splix" package came with all the PPDs, then in later versions they came compressed, and then in the most recent version the source code comes with the package and the PPDs are supposed to be generated at install time. Maybe there is a bug in that process? That would explain the apparent absence of the needed PPD files here.
Thanks!
Related branches
Changed in system-config-printer (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in system-config-printer (Ubuntu): | |
status: | Triaged → In Progress |
status: | In Progress → Fix Committed |
The PPD files are there, but in one compressed archive, /usr/lib/ cups/driver/ splix. You see the PPD files if you let CUPS list them via the command
lpinfo -m
Run
lpinfo -m | grep 1740
in a terminal window and you see all possibilities for your printer.
When I run system- config- printer (I do not have any Samsung printer) and enter the URI "x:" under "Enter URI" I get into the step of manually choosing make and model. There I choose "Samsung" and "ML-1740". The SpliX driver appears there, but indeed the "gdi" driver is marked recommended. This wrong assignment is done by a prioritarization in system- config- printer, it seems to have gotten messed up on the recent change of handling driver priorities.
Moving the bug to system- config- printer ...