Bug 14270

Summary: Recent breakage - existing printer PPD deleted
Product: Mageia Reporter: Frank Griffin <ftg>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: Normal CC: eeeemail, wilcal.int, zen25000
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: system-config-printer CVE:
Status comment:

Description Frank Griffin 2014-10-12 19:28:00 CEST
Not quite sure who owns this, but I'll start with S-C-P.

I have a cauldron system which has a USB HO Multifunction attached.  I went to print something a few days ago, and although I got a "print job completed" notification pop-up, nothing was printed.

Digging into this a bit, I found an error message to the effect that /etc/cups/ppd/lp0.ppd did not exist.

SCP still listed the printer, so I deleted it and tried to redefine it.  The printer showed up in the selection list, but selecting it got no response from SCP.

I went into CUPS administration and tried Add Printer.  Again, the printer was listed as a choice, but in CUPS everything worked, I was given a driver selection dialog (which I was not in SCP), and the definition completed and the printer worked fine.

So, two issues.  Who deleted the PPD file, and why was SCP unable to redefine the printer ?

Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2014-11-04 00:01:22 CET
system-config-printer has been updated to 1.5.3.  Any better luck?

Keywords: (none) => NEEDINFO

Comment 2 Frank Griffin 2014-11-04 15:42:40 CET
Worse.  The new S-C-P hangs while searching for drivers (I think this has been reported elsewhere).

Happens for both an HP MultiFunction and an Epson Inkjet.

CUPS "Add Printer" works fine.
Comment 3 Barry Jackson 2014-12-15 01:47:16 CET
Yes worse for me too.

I have a Samsung-SCX-4521F multifunction laser printer.
It was working in Cauldron *without* the following installed:
system-config-printer
task-printing-server
task-printing-hp

Now on going into mcc -> Configure printing & scanning -> Set up the printer...
an install of the above packages is forced.

The "printer" instance that I had previously still works, and thankfully I have not deleted it :)
Log when printing using that one shows:-
[14/Dec/2014:23:37:35 +0000] "POST /printers/Samsung-SCX-4521F HTTP/1.1" 200 418 Print-Job successful-ok

 but on adding a new instance of same printer as before after recent updates it is detected as "Samsung-SCX-4x24 Series PXL" and in properties it offers "Print Head Cleaning" as an option which is odd for a Laser printer!

It fails to print a test page, the dialog shows "Page Submitted" and the LCD on the printer shows:
Printing - Please Wait
Printing...
Ready
but nothing happens at all and no errors are displayed anywhere.
Log shows:-
[15/Dec/2014:00:18:24 +0000] "POST /printers/Samsung-SCX-4x21-Series HTTP/1.1" 200 424 Print-Job successful-ok

Note the different printer number Samsung-SCX-4x21-Series. No idea yet about the 200 424 as opposed to 200 418 above.

I see similar if I connect it to an old machine (pIII) running Cauldron - the printer is detected again as Samsung-SCX-4x21-Series and the LCD shows PC-print... but nothing is printed (noises are made but no paper is picked up).

lsusb shows:
Bus 003 Device 003: ID 04e8:3419 Samsung Electronics Co., Ltd Composite Device

I really want to get this working on the pIII machine which was running Mga4. where it also failed to print. I upgraded it last night to Cauldron as I knew that it *was* working on my main cauldron machine. :\

CC: (none) => zen25000

Barry Jackson 2014-12-16 17:47:32 CET

Severity: normal => critical

claire robinson 2014-12-17 17:17:01 CET

CC: (none) => eeeemail, wilcal.int

Comment 4 Barry Jackson 2014-12-20 16:32:59 CET
OK - It seems that the detected printer which is recommended in the list is incorrect. By chance I found the correct driver listed (out of alphabetical sort order - which is why I missed it previously) and this does install and work correctly.
No printer is detected however without first installing task-printing. Just which of the 50+ packages this installs are actually required I have yet to discover, however I am suspecting cups-drivers-splix, why is this not installed with the drak* printing part of mcc along with the other cups drivers?
Comment 5 Samuel Verschelde 2015-05-19 14:11:56 CEST
Is this problem still present in latest cauldron?
Comment 6 Frank Griffin 2015-05-19 14:23:49 CEST
It worked OK for me in a recent (~1 month ago) cauldron install on the same machine.  Can't speak to Barry's case, though.
Comment 7 Samuel Verschelde 2015-05-19 14:26:07 CEST
Let's close it and let him reopen if needed.

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