Bug 12485 - Printer Samsung M2825ND does not work with the auto-detection of Mageia 4RC
Summary: Printer Samsung M2825ND does not work with the auto-detection of Mageia 4RC
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-01-31 10:14 CET by Jérôme Borme
Modified: 2015-03-07 21:56 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
printers.conf (1.07 KB, text/plain)
2014-01-31 10:16 CET, Jérôme Borme
Details
PPD file provided by Mageia 4RC (34.20 KB, text/plain)
2014-01-31 10:17 CET, Jérôme Borme
Details
PPD file provided by the manufacturer (51.51 KB, application/vnd.cups-ppd)
2014-01-31 10:18 CET, Jérôme Borme
Details

Description Jérôme Borme 2014-01-31 10:14:22 CET
In installed Mageia 4 RC (plus network updates). I connected the computer to Samsung M2825ND printer through USB (regular type A/type B cable)

MCC detects the printer and selects a suitably-named PPD.
* CUPS test page gives garbage
* The «maintenance» tab in MCC has a button that tells me I can get information about the cleanliness of the printing heads. It's a laser printer so it does not really make sense have printing heads, so I pressed it out of curiosity. I got a page printed with some garbage and the following sentence: « If you can read this, you are using the wrong driver for your printer. »

Next, I installed the manufacturer driver (see links below), which includes some binary filters and ppds, and selected that PPD manually, then the printer works fine.

The triage guide suggests to give journalctl --lines=20 2>&1 | tee output.txt
There was nothing useful in this file. 

I attach
* printers.conf
* the two PPD.
Note that the names with -2 suffix refers to the files provided by Mageia, the other one is from the manufacturer.

Link to the manufacturer's driver:
Get ULD_Linux_V1.00.06.tar.gz from http://www.samsung.com/pt/support/model/SL-M2825ND/SEE-downloads
It has a ./install script which can be run once as root to install the filters.


Reproducible: 

Steps to Reproduce:
Comment 1 Jérôme Borme 2014-01-31 10:16:46 CET
Created attachment 4904 [details]
printers.conf

Note that <Printer Samsung-M262x-282x-Series-2> refers to the configuration automatically detected by Mageia, while <Printer Samsung-M262x-282x-Series> is the configuration resulting from manually selecting the PPD provided by the manufacturer.
Comment 2 Jérôme Borme 2014-01-31 10:17:17 CET
Created attachment 4905 [details]
PPD file provided by Mageia 4RC
Comment 3 Jérôme Borme 2014-01-31 10:18:07 CET
Created attachment 4906 [details]
PPD file provided by the manufacturer
Jérôme Borme 2014-01-31 10:19:51 CET

Summary: Printer Samsung M2825ND does not work with included PPD => Printer Samsung M2825ND does not work with the auto-detection of Mageia 4RC

Comment 4 Olivier FAURAX 2014-10-22 15:23:45 CEST
From which package comes the .ppd from Mageia?
If you don't know, simply "urpmf [FILENAME]"

Keywords: (none) => NEEDINFO
CC: (none) => olivier

Comment 5 Marja Van Waes 2014-10-22 16:59:35 CEST
OFF-topic, but maybe useful to someone who searches this printer in our bugzilla 

If you scroll down on this page

http://www.samsung.com/uk/consumer/print-solutions/print-solutions/mono-printers/SL-M2825ND/SEE

You'll see that there is new firmware 
Version : V3.00.01.25
10 Oct, 2014

I can't find the correct character set to read the release notes (or I have a problem reading xlsx files)

For cauldron, btw, I think I used
/usr/share/foomatic/db/source/PPD/Samsung/PXL/Samsung_M262x_282x_Series_PXL.ppd.gz
for this printer, which comes from foomatic-db
However, I don't remember having had a problem in cauldron the few times I printed something on it (via LAN, btw), so maybe the cauldron package is better.

CC: (none) => marja11

Comment 6 Jérôme Borme 2015-03-07 21:56:06 CET
Does not happen with Mageia 5 (beta3)

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.