Is it a flatpak/appimage install?
Tim Evans:
Installed via dnf from the Google Chrome repo
I don't use Chrome, but generically speaking I find that such
applications will rarely print (probably because of the sandboxing
that
isolates them from the system). Sometimes they can, but only with
a printer they've found themselves, not the CUPs printers. And I'm
using an office HP laserjet that's been well-supported for many
years.
Chrome sees the printers.
Oh my problem apps see them, they just can't use them. Printing
just disappears into a black hole.
Going back to your original message:
All efforts to print pages/documents from Google Chrome (Unstable)
(145.0.7587.4) fail
Perhaps try the stable version, instead.
As Doug Herr pointed out, in Chrome-Stable, printers are sorta hidden
behind the "See More" button on the print dialogue, and mine ARE seen
here.
Nevertheless, trying to print from Chrome-Stable also fails--though,
without the pop-up message I mentioned to begin with. Printing just
silently fails.
So, as I said initially, workaround is to save the page as a PDF and
print from the file manager.
Thanks for all the responses.
I have a printer connected to my router so that all devices can see it.
I have 2 definitions for that printer (just to test them out) one using
the headerless cups driver and one using the IPP driver, both of which
have different configuration options. What I've found with the stable
cups printing functionality is it seems to be a two stage process.
As Doug said you have to select the "See More" option to select a
printer, once you do that, for that Chrome session the selected printer
appears in the list with "Print to PDF", but doing that selection
doesn't cause the printing to happen, once you select the printer you
have to do the printing again to that device (which remains the selected
device) for the print to actually happen. If I go through the "See More"
option to select my second printer definition, that printer appears in
the list as well with it highlighted as the device to print to, but the
printing doesn't happen, I have to do the print a second time for the
printer to actually physically print.
The other thing I've noticed is both drivers allow me to select the
paper type I want to print on, but the print dialogue options presented
by Chrome don't allow that selection, I have to use the "Print Using
System Dialogue" to get the ability to change the paper type. The
headerless driver also allows the option of auto scaling of the print,
which is also only selectable if using the system dialogue to do the
configuration for the print.
Firefox has similar configuration deficiencies as Chrome does, although
it does have some rudimentary scaling functionality irrespective of the
destination, but when you select the destination the printing happens
immediately, the Chrome two stage process is not required.
regards,
BEGIN:VCARD
VERSION:4.0
N:Morris;Stephen;;;
FN:Stephen Morris
EMAIL;PREF=1;TYPE=home:[email protected]
END:VCARD
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
