Description of problem: I have just upgraded from Fedora35 to 36 and now cannot print in colour. No changes were made to the printer setup during upgrade. I have to print using "socket" connection and ppd as the "driverless" option does not work well with this printer. Version-Release number of selected component (if applicable): cups 2.4.1 How reproducible: Easy Steps to Reproduce: 1.Select "full colour" from print dialog 2.Print document. 3. Actual results: Document prints in B&W only Expected results: Document prints in colour Additional info: Fedora presents a "discovered" printer in the Gnome settings, which despite being visible still needs to be "Added" before it will work. This setup will enable colour printing but only a small set of the available printer options are presented in the print dialogs. I need to use options that are not available via the driverless install, so I use a socket connection and ppd file (downloaded from Kyocera website) to get more functionality. Complete functionality is available via the Kyocera "kyodialog" available from their website but does not detect the driverless setup. I am able to get colour output with the socket connection by installing kyodialog-9.1 (downloaded from Kyocera website) and printing an image to "LPR" from the Gnome Image Viewer.
Hi, thank you for reporting the issue! It would be great if you provided the data according the steps mentioned here https://docs.fedoraproject.org/en-US/quick-docs/how-to-debug-printing-problems/#_my_printer_doesnt_print_correctly_or_at_all_but_i_can_see_the_printer_in_print_dialog Thank you in advance!
Created attachment 1880804 [details] CUPS error log
Created attachment 1880805 [details] lpinfo -l -v
(In reply to Neil Romig from comment #0) > Additional info: > Fedora presents a "discovered" printer in the Gnome settings, which despite > being visible still needs to be "Added" before it will work. Can you print to the discovered printer in Evince or Libreoffice without adding the printer? If it works, then the temporary queue (that's the term for it) can be used. In case you had to add the printer manually because it wasn't shown in Firefox or the entry in Control Center looked broken and the testing page didn't work, they are known bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1765328 https://bugzilla.redhat.com/show_bug.cgi?id=1983403 The nonfunctional entry for temporary queue in G-C-C does not have an impact on printing itself, the printer usually works when you are in a print dialog itself, and Firefox provides an option to switch into system print dialog, which is written in GTK on GNOME desktop, thus supports temporary queues. > This setup will > enable colour printing but only a small set of the available printer options > are presented in the print dialogs. Would you mind attaching output of ipptool command (see https://docs.fedoraproject.org/en-US/quick-docs/how-to-debug-printing-problems/#_cups_everywhere_model) if you use IPP? Then it would great if you told me which essential options you use and they're missing in driverless install. ====================================================================================================================== Ad the provided data: Thank you for the provided data! Would you mind providing your PPD (/etc/cups/ppd/Kyocera_TASKalfa_2552ci.ppd) as well? Ad logs: I can see there is the default option for monochrome: D [18/May/2022:12:50:03 +0100] [Job 251] Applying default options... D [18/May/2022:12:50:03 +0100] [Job 251] Adding default print-color-mode=monochrome D [18/May/2022:12:50:03 +0100] add_job: requesting-user-name="yul" I [18/May/2022:12:50:03 +0100] [Job 251] Adding start banner page "none". which is applied among print job options which came from the application: D [18/May/2022:12:50:03 +0100] [Job 251] argv[5]="Resolution=600dpi JCLTrapping=Medium CIE=PrnDef OutputBin=None noKCGlossmode PageSize=A4 KCFoldB=None StapleCount=None Duplex=DuplexNoTumble RCM=PrnDef noGRAYBLKTONER MediaType=PrnDef InputSlot=PF730A noOverprint noRotate noKCRotate KCHalftone=Normal ColorModel=CMYK KCFoldD=None KCEcoprint=Off KCFoldC=None Smoothing KCCollate=PrnDef KmManagment=Default noCollate number-up=1 Colorreprod=Printersettings KCBooklet=None job-uuid=urn:uuid:21059497-3797-379c-5801-b180706183a3 print-color-mode=monochrome job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1652874603 time-at-processing=1652874603" See the options: ColorModel=CMYK and print-color-mode=monochrome We had a fix related to color printing upstream in 2.4.1, maybe this is a regression after that.
(In reply to Zdenek Dohnal from comment #4) CUPS makes my head spin it is so complicated but I'll try to keep up! I am not sure what to use as "<your_printer_device_uri>" in the ipptool command line, and not even sure if I use IPP? Some discoveries: 1) I can delete the printer from Gnome settings and it will reappear. I can print to it straight away using LibreOffice but initially the Gnome printer setup shows a blank dialog box for "Printing Options", and LibreOffice has almost no usable options in the print dialog. After the first document print the Gnome "Printing Options" has a set of usable options as does the LibreOffice print dialog, but these will disappear shortly after printing. In short - the printer options are only available briefly after printing (which is of course useless). 2) If I "add" the printer, the Gnome setting "Printer Details" address changes from (null) to (localhost), the name shown changes from "Kyocera_TASKalfa_2552ci" to "Kyocera-TASKalfa-2552ci", the model goes from "Kyocera Kyocera TASKalfa 2552ci (KPDL)" to "TASKalfa 2552ci (driverless)", and the basic set of printer options become permanent. And, yes, Firefox does not show the printer until it is manually added. The main option missing that I use is ability to print to the hard drive of the printer. This is referred to as "Custom Box" and is very useful to me.
Created attachment 1881563 [details] Kyocera PPD This is the ppd file from Kyocera website as part of the kyodialog package.
Created attachment 1881603 [details] CUPS error log x2 This file shows two print jobs - the first using driverless queue which prints in colour, the second using socket connection w/Kyocera ppd which prints only in monochrome.
Created attachment 1881608 [details] ipptool output (driverless) ipptool --ippserver ipptool.attr ipp://localhost:631/printers/Kyocera-TASKalfa-2552ci get-printer-attributes.test
Created attachment 1881609 [details] ipptool output (socket) ipptool --ippserver ipptool.attr ipp://localhost:631/printers/KyoceraTASKalfa2552ci get-printer-attributes.test
Hi Neil, there is CUPS 2.4.2 in testing - are you able to reproduce the issue with it? With new version I'm able to print color/b&w as before the issue.
(In reply to Zdenek Dohnal from comment #10) > Hi Neil, > > there is CUPS 2.4.2 in testing - are you able to reproduce the issue with > it? With new version I'm able to print color/b&w as before the issue. Yes, issue still exists. Unable to print colour using socket connection & Kyocera ppd (checked by printing test page from Gnome printer settings). Driverless connection prints colour but lacks functionality.
Hi Neil, here I have a testing rpms which should fix color printing via socket+classic ppd - https://koji.fedoraproject.org/koji/taskinfo?taskID=90399669 Would you mind testing them?
(In reply to Zdenek Dohnal from comment #12) > https://koji.fedoraproject.org/koji/taskinfo?taskID=90399669 I was also affected by printing only black&white and the RPMs above fixed that for me, I can now print in color.
Hi Neil and Kamil, I've found one more use case which I had to cover, so there are testing rpms - https://koji.fedoraproject.org/koji/taskinfo?taskID=91210382 Would you mind testing them?
Hi, sorry, I don't have access to that printer right now and I'm leaving for a vacation soon. I suggest submitting the build to updates-testing and have it tested by more people.
(In reply to Kamil Páral from comment #15) > Hi, sorry, I don't have access to that printer right now and I'm leaving for > a vacation soon. I suggest submitting the build to updates-testing and have > it tested by more people. The fix is not in upstream yet, I wanted to verify the fix downstream, then get it upstream and after that do a production build which can go into updates-testing. I have one feedback from another bug and I've verified the bugs myself as well, so I will not wait and pass this upstream. Once you are back and have a time to test, it would be great to leave a feedback :) .
FEDORA-2023-b6b1ff44a5 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b6b1ff44a5
FEDORA-2023-c5cf4f6be2 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c5cf4f6be2
FEDORA-2023-7ceae7b00b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ceae7b00b
FEDORA-2023-b6b1ff44a5 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b6b1ff44a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-c5cf4f6be2 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c5cf4f6be2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c5cf4f6be2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-7ceae7b00b has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-7ceae7b00b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ceae7b00b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-c5cf4f6be2 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-b6b1ff44a5 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-7ceae7b00b has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
The CUPS printing system is failing me. I used to be able to print without problems using the socket connection and drivers supplied by Kyocera. Now this is deprecated, and the IPP-based approach simply is not working. I am having serious thoughts as to whether I should continue to struggle with CUPS or just stick with Windows for printing. Is there a way to install an old version of CUPS??
(In reply to Neil Romig from comment #26) > The CUPS printing system is failing me. I used to be able to print without > problems using the socket connection and drivers supplied by Kyocera. Hi Neil, do you mean a problem with color setting or something else? I do test the new RPMs on my printers to see whether it works or not, but I don't try all applications and I'm not able to reproduce if the issue is happening with a specific hardware. In such cases cooperation with the reporter is mandatory, so I know whether the fix helps the reporter or not. Unfortunately there has been no response from you for seven months, so I took Kamil's verification into account and backported fixes several months later (I thought I would manage a new release incorporating the fixes, but I haven't been able to make it so far). > Now > this is deprecated, and the IPP-based approach simply is not working. Until drivers are dropped from CUPS completely and printer applications are not packaged, I'll do my best to help regarding classic drivers. ========================================== To sum it up: 1) it would be great if you told me what is the issue - in case there is a different issue from the original issue about color settings, please file a separate bugzilla 2) enable debug logging in CUPS ($ cupsctl LogLevel=debug2), reproduce the issue and attach a new file to the bugzilla.
OK, first let me apologise for not getting around to this sooner, but you know how things just get shunted to the end of the line... Having updated my Fedora and received 2.4.2-10 I can confirm I am able to print in colour and use the "traditional" socket connection with all printer facilities as provided via the Kyocera software. This means the issue is closed as far as I am concerned, and I will probably be keen to keep cups "as is" until such time as I have access to a newer / better printer and can switch to IPP. As a final remark, I recently had to setup a Windows 11 PC and in allowing it to configure the printer it chose IPP for the task. The resulting print dialog was almost as lacking in options as the CUPS driverless setup in Linux, so I suspect the Kyocera TASKalfa 2552ci just has bad IPP support and the socket connection is the only way to achieve full functionality.