Description of problem: Version-Release number of selected component (if applicable): Lost my printer having updated from f31 to f32, How reproducible: Every time Steps to Reproduce: 1. I tried to associate print on KDE dialog. 2. 3. Actual results: Mar 27 17:47:15 tigger2 cupsd[1069]: REQUEST localhost - - "POST / HTTP/1.1" 200 6597474 CUPS-Get-PPDs - Mar 27 17:47:15 tigger2 cupsd[1069]: REQUEST localhost - tim "POST / HTTP/1.1" 200 6597502 CUPS-Get-PPDs - Mar 27 17:47:21 tigger2 cupsd[1069]: [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipp://Canon%20TR8500%20series._ipp._tcp.local/, ipp://000000668D30.local:631/ipp/print) via IPP! Mar 27 17:47:21 tigger2 cupsd[1069]: copy_model: empty PPD file Mar 27 17:47:21 tigger2 cupsd[1069]: [Client 45] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://tim@localhost:631/printers/Canon_TR8500_series) from localhost. Mar 27 17:47:21 tigger2 cupsd[1069]: REQUEST localhost - tim "POST /admin/ HTTP/1.1" 200 666 CUPS-Add-Modify-Printer server-error-internal-error Mar 27 17:47:21 tigger2 kde-add-printer[54621]: libkcups: IPP_INTERNAL_ERROR: clearing cookies and reconnecting Mar 27 17:47:21 tigger2 kde-add-printer[54621]: libkcups: Failed to reconnect Invalid argument Mar 27 17:47:21 tigger2 cupsd[1069]: [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipp://Canon%20TR8500%20series._ipp._tcp.local/, ipp://000000668D30.local:631/ipp/print) via IPP! Mar 27 17:47:21 tigger2 cupsd[1069]: copy_model: empty PPD file Mar 27 17:47:21 tigger2 cupsd[1069]: [Client 45] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://tim@localhost:631/printers/Canon_TR8500_series) from localhost. Mar 27 17:47:21 tigger2 cupsd[1069]: REQUEST localhost - tim "POST /admin/ HTTP/1.1" 200 666 CUPS-Add-Modify-Printer server-error-internal-error Mar 27 17:47:21 tigger2 kde-add-printer[54621]: libkcups: IPP_INTERNAL_ERROR: clearing cookies and reconnecting Mar 27 17:47:21 tigger2 kde-add-printer[54621]: libkcups: Failed to reconnect Invalid argument Mar 27 17:47:22 tigger2 cupsd[1069]: [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipp://Canon%20TR8500%20series._ipp._tcp.local/, ipp://000000668D30.local:631/ipp/print) via IPP! Mar 27 17:47:22 tigger2 cupsd[1069]: copy_model: empty PPD file Mar 27 17:47:22 tigger2 cupsd[1069]: [Client 45] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://tim@localhost:631/printers/Canon_TR8500_series) from localhost. Mar 27 17:47:22 tigger2 cupsd[1069]: REQUEST localhost - tim "POST /admin/ HTTP/1.1" 200 666 CUPS-Add-Modify-Printer server-error-internal-error Mar 27 17:47:22 tigger2 kde-add-printer[54621]: libkcups: IPP_INTERNAL_ERROR: clearing cookies and reconnecting Mar 27 17:47:22 tigger2 kde-add-printer[54621]: libkcups: Failed to reconnect Invalid argument Expected results: An Associated printer Additional info:
Hi Tim, thank you for reporting the issue! Would you mind trying to reproduce the issue without kde-print-manager? Most of error messages comes from its library and the important message: Mar 27 17:47:21 tigger2 cupsd[1069]: [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipp://Canon%20TR8500%20series._ipp._tcp.local/, ipp://000000668D30.local:631/ipp/print) via IPP! has the error reason which is not defined in CUPS... But it seems your printer supports IPP everywhere (driverless standard) and the error happens during creating PPD from printer's IPP response. How to reproduce without kde-print-mananger: 1) List the available devices: $ sudo lpinfo -l -v 2) Find the device uri of your Canon printer (it looks it is ipp://Canon%20TR8500%20series._ipp._tcp.local/) in the list and try to add it as IPP everywhere model: $ sudo lpadmin -p <name_of_your_choice> -v ipp://Canon%20TR8500%20series._ipp._tcp.local/ -m everywhere -E If the queue is created correctly this way and you are able to print, I would say the error is on kde-print-manager's side. If the error is reproducible even by those commands, please follow the steps https://fedoraproject.org/wiki/How_to_debug_printing_problems#B._Capture_whole_CUPSD_log , capture logs during the step 2) and attach the file as an attachment.
Ok looks like a KDE problem. It happened after an update from f31 to f32 beta (not before). Ran you commands Device: uri = ipp://Canon%20TR8500%20series._ipp._tcp.local/ class = network info = Canon TR8500 series (driverless) make-and-model = Canon TR8500 series device-id = MFG:Canon;MDL:TR8500 series;CMD:PWGRaster,AppleRaster,JPEG,URF,PWG; location = ➜ ~ ipp://Canon%20TR8500%20series._ipp._tcp.local/ zsh: no such file or directory: ipp://Canon%20TR8500%20series._ipp._tcp.local/ ➜ ~ sudo lpadmin -p study -v ipp://Canon%20TR8500%20series._ipp._tcp.local/ -m everywhere -E Added printer fine. Just printed from libreoffice writer works fine. Printing from chrome does not at present. Mar 30 09:55:12 tigger2 cupsd[1072]: REQUEST localhost - - "POST / HTTP/1.1" 200 543 Create-Printer-Subscriptions successful-ok Mar 30 09:55:15 tigger2 cupsd[1072]: REQUEST localhost - - "POST / HTTP/1.1" 200 151 Cancel-Subscription successful-ok Mar 30 09:55:15 tigger2 cupsd[1072]: REQUEST localhost - - "POST / HTTP/1.1" 200 355 Create-Printer-Subscriptions successful-ok Mar 30 09:55:15 tigger2 cupsd[1072]: REQUEST localhost - - "POST / HTTP/1.1" 200 151 Cancel-Subscription successful-ok Mar 30 09:55:15 tigger2 kwin_x11[1660]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19888, resource id: 132120592, major code: 18 (ChangeProperty), minor code: 0 Mar 30 09:55:49 tigger2 configure-printer[8887]: kf5.kwidgetsaddons: Invalid pixmap specified. Mar 30 09:55:49 tigger2 configure-printer[8887]: kf5.kwidgetsaddons: No frame loaded Mar 30 09:55:49 tigger2 configure-printer[8887]: kf5.kwidgetsaddons: No frame loaded Mar 30 09:55:49 tigger2 configure-printer[8887]: kf5.kwidgetsaddons: No frame loaded Mar 30 09:55:56 tigger2 cupsd[1072]: Canon_TR8500_series tim 182 [30/Mar/2020:09:55:56 +0100] total 1 - localhost Untitled 2 - - Mar 30 09:56:08 tigger2 cupsd[1072]: Job aborted because the destination printer/class has gone away from the log file when doing the printing. Not seeing anything on the KDE print queue.
(In reply to TR Bentley from comment #2) > zsh: no such file or directory: > ipp://Canon%20TR8500%20series._ipp._tcp.local/ > ➜ ~ sudo lpadmin -p study -v ipp://Canon%20TR8500%20series._ipp._tcp.local/ > -m everywhere -E > > Added printer fine. > > Just printed from libreoffice writer works fine. > Printing from chrome does not at present. > > Mar 30 09:55:56 tigger2 cupsd[1072]: Canon_TR8500_series tim 182 > [30/Mar/2020:09:55:56 +0100] total 1 - localhost Untitled 2 - - > Mar 30 09:56:08 tigger2 cupsd[1072]: Job aborted because the destination > printer/class has gone away > > > from the log file when doing the printing. > It looks like you printed to temporary queue (which is used properly in libreoffice), not to permanent one which you created. And Chrome seems to try to print to temporary queue, but it is not able to work with it properly (Chrome issue).
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.