When I open Settings, go to Printers, and click Unlock, I see my printer (HP LaserJet m551dn) listed there even though I haven't added it. However, it doesn't work. When I go to Printing Options and click Test Page, nothing happens. When I go to Printer Details it says that the address of the printer is "(null)". When I click the Add Printer... button, wait until it finds the printer on the network, and add that printer, it DOES work; it's just the printer added automatically that doesn't. Also, the Settings app seems to sporadically crash when doing all this, though not every time so I'm not sure it's relevant. :shrug:
Thanks Jonathan! I have a similar problem on F37, except that "Add Printer..." also doesn't work; it creates a printer, but neither printing a test page nor attempting to use it (in my case from Firefox) ever works (over several attempts). I have a HP Color LaserJet MFP M281fdw, network connected. When I restored /etc/cups from my backup done on F36 from a setup I did several years ago while initially installing the system and restart cups, I can now print using the printer definition that it finds there.
I found the logs that explain the difference in our experience: cupsd[1067]: [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipps://HP%20Color%20LaserJet%20MFP%20M281fdw%20(B1AC20)._ipps._tcp.local/, ipps://NPIB1AC20.local:631/ipp/print) via IPP! cupsd[1067]: copy_model: empty PPD file cupsd[1067]: [Client 59] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/HP-ColorLaserJet-MFP-M278-M281) from localhost. This is not surfaced through the UI. Like Jonathan, I saw Settings crash a few times while trying to set up printing.
The further I look, the more I think I'm affected by two separate bugs; I'll file a separate bug.
I have filed #2148500 for my printer not working even when added manually.
Hi Jonathan, thank you for reporting the issue! Are you able to print from an application you use for viewing documents? Like Firefox/Evince (PDF Viewer)/Libreoffice? I've prepared a testing rpms for gnome-control-center, which should let you print test page - https://koji.fedoraproject.org/koji/taskinfo?taskID=94645162 . Do let me know if it helps, so I can pass the fix to g-c-c. Thank you in advance!
Oh, interesting. It didn't occur to me that this was a g-c-c issue rather than a cups issue. Yes, I am able to print to the automatically added printer from other apps. Not only that, but if I leave g-c-c open and print from another app then go back to g-c-c I am able to print a test page successfully. Your g-c-c try build does allow me to print a test page right away, but there is one remaining issue I just noticed: the Printing Options window is empty, i.e., the options are not visible, when I open it immediately after the printer appears in g-c-c. However, if I print a test page and then close and open the Printing Options window again the options appear. All in all just not an incredibly smooth experience. :-/
(In reply to Jonathan Kamens from comment #6) > Oh, interesting. It didn't occur to me that this was a g-c-c issue rather > than a cups issue. It is a good start to suspect the specific application instead of generic system daemon if other apps work to some extent. Sure, there can be an issue in the daemon's library which the application uses, but that's the best to be reviewed by the application maintainer. For printing issue is a good practice to check whether the printer works via CUPS CLI commands: $ lpstat -e to check whether your printer is seen by CUPS, $ lp -d <name_from_previous_cmd> <small_usually_one_page_long_file_f.e._/etc/fstab> to check whether the printer is able to print. > > Yes, I am able to print to the automatically added printer from other apps. That's great, thanks! > Not only that, but if I leave g-c-c open and print from another app then go > back to g-c-c I am able to print a test page successfully. It is due the nature of temporary queues - they created just for printing and then they hang out for another minute till they are removed. In that time frame g-c-c is able to access them. > > Your g-c-c try build does allow me to print a test page right away, but > there is one remaining issue I just noticed: the Printing Options window is > empty, i.e., the options are not visible, when I open it immediately after > the printer appears in g-c-c. This is a known issue as https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1877 . > However, if I print a test page and then close > and open the Printing Options window again the options appear. It is the same effect as before - it is a time frame when the temporary queue is set up. > > All in all just not an incredibly smooth experience. :-/ I'm sorry for inconvenience - upstream is working on making it better. Regarding this bugzilla I would rename it to 'g-c-c cannot print test page for temporary queue' and add the link to upstream PR, since the printing options are already tracked upstream. The upstream PR is https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1516 .
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
The PR is merged and printing test page works in F38 - I'm not sure about F37, I don't have F37 anymore.