Bug 24968 - Printing to Samsung C410W fails with "SPL-C ERROR - Illegal Resolution"
Summary: Printing to Samsung C410W fails with "SPL-C ERROR - Illegal Resolution"
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-16 22:40 CEST by Juergen Harms
Modified: 2019-07-29 14:39 CEST (History)
4 users (show)

See Also:
Source RPM: system-config-printer-1.5.11-2.mga7.src.rpm
CVE:
Status comment:


Attachments
console output while doing command-line system-config-printer (2.03 KB, text/plain)
2019-06-17 23:00 CEST, Juergen Harms
Details

Description Juergen Harms 2019-06-16 22:40:31 CEST
Description of problem:

I can configure my Samsung C410W color laser printer, but when I print to it (even the test page during the configuration process) the printer always prints a page with the content

SPL-C ERROR - Illegal Resolution
    POSITION : 0xff6a (65386)
    SYSTEM   : src/xl_tbi
    LINE     : 858
    VERSION  : SPL-C 5.59.01 06-19-2013

Notes:

1. This printer is not contained in the standard list of drivers, its driver needs to be manually installed from a package downloaded from the Samsung (resp. HP) support site at https://ftp.hp.com/pub/softlib/software13/printers/SS/SL-C4010ND/uld_V1.00.39_01.17.tar.gz

2. On Mageia-6 both installation and printing work without problem.

3. On cauldron, system-config-printer proposes as connection "IPP", which needs to be corrected to "AppSocket/HP JetDirect" - otherwise a connection is not established.

4. Since, with the same device-specific driver (and the same .ppd file), printing works in Mageia-6 but not in Mageia-7, it is likely that some other Samsung-specific component causes the problem (when the Samsung 410 is configured, some ten packages are pulled in, several of them referring to Samsung printers). Googling for "Samsung SPL-C error" indicates that Samsung SPL error messages are quite frequent both on Linux and Windows, but no evident reason stands out. 


Version-Release number of selected component (if applicable):


How reproducible:

Always


Steps to Reproduce:
1. Download and install the driver
2. Standard printer configuration procedure with system-config-printer, setting "Connection" to "AppSocket/HP JetDirect" (network printer in my case)
3. print a page - for instance the printer testpage


I use - and have access to - the Samsung 410 printer only when I am on vacation with my family - presently that ends in 10 days. But I think it is important to document the problem and file a bug - very probably other Samsung printers will be concerned.
Comment 1 Juergen Harms 2019-06-17 23:00:27 CEST
Created attachment 11100 [details]
console output while doing command-line system-config-printer
Comment 2 Marja Van Waes 2019-06-19 12:24:27 CEST
Assigning to the registered maintainer, CC'ing three submitters

CC: (none) => geiger.david68210, luigiwalser, marja11, tmb
Assignee: bugsquad => mageia

Comment 3 Juergen Harms 2019-06-22 22:45:50 CEST
> ... presently that ends in 10 days

Please forget this: I will take the printer with me when I go back to Geneva.
Comment 4 Juergen Harms 2019-07-29 10:42:12 CEST
In the meantime I have
- Googled for other instances of this problem  happening and found several on other Linux distros, e.g. https://askubuntu.com/questions/1141036/printer-problems-with-samsung-c410w-after-upgrade-to-19-04
- Eliminated the hypotheses (suggestions by google hits) on not sufficiently short cables (problem arrives also if configured as network printer - wired net)
- Verified that the printer works perfectly on Windows 10 (and - using windows - updated the printer firmware) (no improvment on Linux)
- Realised that the printer is not very popular among Linux users,
- Decided that I am loosing my time (I have ordered an hp MFP M281fdw as a replacement) - dito for the time of the bug squad.

What keyword to use for closing the bug ?
Comment 5 David Walser 2019-07-29 13:35:02 CEST
WONTFIX or OLD.
Comment 6 Juergen Harms 2019-07-29 14:39:41 CEST
See comment 4

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


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