Description of problem: The output using the free Samsung CLP-315 printer driver is too dark. Version-Release number of selected component (if applicable): 64 bit Mageia 5, however, I also had the problem on 32 bit Mageia 4. How reproducible: Always Steps to Reproduce: 1. Print something (the test page works) using Mageia's driver (Samsung CLP-310 or 315 Foomatic/foo2qpdl [en]), either one 2. It is too dark, especially noticeable in color 3. Install Samsung's proprietary driver 4.x and pick that driver (Samsung CLP-310 series [en]) 4. Print the same test page. It is okay. This bug was supposedly fixed long ago in another distribution as https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/378068 . I don't know if this fix is in Mageia and don't know how to check. Reproducible: Steps to Reproduce:
Blocks: (none) => 18367
On the 25th of July, Phillipem uploaded the following packages to Cauldron's core/updates_testing: system-config-printer-1.5.7-5.mga6.i586 system-config-printer-applet-1.5.7-5.mga6.i586 system-config-printer-udev-1.5.7-5.mga6.i586 system-config-printer-libs-1.5.7-5.mga6.noarch system-config-printer-1.5.7-5.mga6.x86_64 system-config-printer-applet-1.5.7-5.mga6.x86_64 system-config-printer-udev-1.5.7-5.mga6.x86_64 @ Anyone reading this: * If this bug is valid for you in cauldron, then please test whether updating your system-config-printer packages to version 1.5.7-5.mga6 fixes the problem and report back in this bug report. * If you do not have this bug in cauldron, but you do run cauldron, then please update those packages, too, and report in bug 18367 whether they work as expected.
CC: (none) => makowski.mageia, marja11
I don't have cauldron. What can I do?
(In reply to Ken Arromdee from comment #2) > I don't have cauldron. What can I do? If possible, you could install the latest version using network install: http://www.mageia.org/en/6/ (prefer network install over ISOs because the ISOs are quite outdated for now).
(In reply to Samuel Verschelde from comment #3) > (In reply to Ken Arromdee from comment #2) > > I don't have cauldron. What can I do? > > If possible, you could install the latest version using network install: > http://www.mageia.org/en/6/ (prefer network install over ISOs because the > ISOs are quite outdated for now). And now you can install Mageia 6 RC, or use a 6RC Live DVD to test.
Keywords: (none) => NEEDINFO
@ Ken Please report whether the issue is solved in Mageia 6
No reply, and, apart from security fixes, no more fixes are pushed to Mageia 5. Closing as OLD
Resolution: (none) => OLDStatus: NEW => RESOLVED
Years later, I am installing Mageia 7.1. This bug still exists in Mageia 7.1. The fix is: 1) Use the foo2qpdl driver. 2) Install a version of Ghostscript 8.71 (https://www.ghostscript.com/GPL_Ghostscript_8.71.html) as /usr/bin/gs.foo. This is a known ghostscript bug (see http://foo2qpdl.rkkda.com/INSTALL under "GHOSTSCRIPT BUGS"), and foo2qpdl-wrapper specifically looks for the name "gs.foo" as a substitute version of gs to avoid the bug. 3) Get the ICM profile for the printer by searching for samclp315-argyll-0.icm (which I believe is not a file Mageia can legally distribute). Put this file in /usr/share/foo2qpdl/icm . Steps 2 and 3 are both required; the result is still a little too dark, but at least readable. Using the proprietary Samsung 4.0 driver from http://www.bchemnet.com/suldr/suld.html (don't try the ones on Samsung's own site) should also work; it worked in previous Mageia versions. Unfortunately, on Mageia 7.1, Samsung's driver doesn't work because of https://github.com/apple/cups/issues/5562 .
Version: 5 => 7
Resolution: OLD => (none)Status: RESOLVED => REOPENED
https://www.samsung.com/uk/support/computing/where-can-i-find-drivers-software-and-support-for-my-samsung-printer/ Samsung printers are no longer supported by Samsung but by HP who acquired Samsung Printers division. For your printer, there is Linux drivers here: https://support.hp.com/gb-en/drivers/selfservice/samsung-clp-315-color-laser-printer-series/19133860 upstream bug is closed and fix in cups 2.2 series. Also, as a warning, upstream cups developers say PPD files have been deprecated in CUPS for 10 years and printer driver support is scheduled to be dropped after CUPS 2.3.x. Current Ghostscript in mga8 is version 9.52.
Status: REOPENED => RESOLVEDCC: (none) => ouaurelienResolution: (none) => OLD
Mageia 8, still having the problem (though the cups upstream bug was fixed). This bug literally requires version 8.71, not 9.52 and it literally requires it be installed under the filename "gs.foo", solely to work around unfixed ghostscript bugs that keep it from working. And this is all documented, in fact, including the number "8.71". The original link is bad, but you can google up foo2qpdl and "GHOSTSCRIPT BUGS". It's right there. I understand that ghostscript has advanced beyond 8.71 but, in fact, 8.71 is necessary to fix the problem. I personally verified this by printing a test page using the foo2qpdl driver and with and without the Ghostscript 8.71 and the .icm file and confirming that I actually do need both of these, and that without either of them the output is too dark (and it's not great even with those, but better). I also personally confirmed that on a new installation of Mageia 8, /usr/bin/foo2qpdl-wrapper contains lines that specifically check for a special version of Ghostscript installed under the name "gs.foo". Furthermore, if I use the clp310.ppd driver instead, the result is too red, and specifically the third item on the Mageia test page (penguin, color wheel, grayscale, Cups logo) has red in the "greyscale" part; the foo2qpdl driver does not have this problem.
Resolution: OLD => (none)Version: 7 => 8Status: RESOLVED => REOPENED
(In reply to Ken Arromdee from comment #9) > Mageia 8, still having the problem (though the cups upstream bug was fixed). > > This bug literally requires version 8.71, not 9.52 and it literally requires > it be installed under the filename "gs.foo", solely to work around unfixed > ghostscript bugs that keep it from working. And this is all documented, in > fact, including the number "8.71". The original link is bad, but you can > google up foo2qpdl and "GHOSTSCRIPT BUGS". It's right there. I understand > that ghostscript has advanced beyond 8.71 but, in fact, 8.71 is necessary to > fix the problem. > We can't have a outdated ghostscript package in our distribution. This should be reported upstream for ghostscript developers. I'm very sorry your printer can not run well under Mageia Linux. https://github.com/apple/cups/issues/5562 is closed upstream. According to you, we should package GS with a /usr/bin/gs.foo binary? Assigning globally and adding Stig as recent committer on this.
CC: (none) => smelrorSource RPM: (none) => ghostscript-9.53.3-2.mga8.src.rpmKeywords: NEEDINFO => (none)Assignee: bugsquad => pkg-bugsStatus: REOPENED => NEW
The gs.foo binary is half the problem. The other half is the .icm file which I don't think Mageia can legally distribute. There is some way of getting it other than Googling it, which I don't remember. You need both to have any effect. But you do package a foo2qpdl script that looks for the file "gs.foo" so there's nothing inherently silly about actually packaging the file that it looks for.