Bug 31648 - google-chrome and chromium refuse to print on remote printer that xpdf, okular, firefox, lp, lpr all print to
Summary: google-chrome and chromium refuse to print on remote printer that xpdf, okula...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-09 00:43 CET by w unruh
Modified: 2023-05-08 20:19 CEST (History)
1 user (show)

See Also:
Source RPM: chromium-browser-110.0.5481.177-1.mga8
CVE:
Status comment:


Attachments
cups error.log file on local machine (17.99 KB, text/plain)
2023-03-09 00:55 CET, w unruh
Details

Description w unruh 2023-03-09 00:43:26 CET
Description of problem:
When trying to print a page on google-chrome or on chromium, I get a "Selected printer not available or not installed correctly" error message for some printers which are linked to a printer on another machine. In all cases, lpr, lp, xpdf, okular all print files without trouble. 
I see no problems in the error.log (cups set to "debug" for logging) but on the local machine there are about 50 lines of output into cups error.log
noe of which are illuminating to me. 

Version-Release number of selected component (if applicable):cups-2.3.3op2-1.mga8  
chromium-browser-108.0.5359.124-1.mga8


How reproducible: Always


Steps to Reproduce: 1. Open a page on chromium or chrome. right click on the page, and select Print. Choose the remote printer. Get the page with the error message.
2. Do the same on Firefox, and the page prints. 
3.Open a pdf file with okular, xpdf, and print-- no problem.
4. With that remote printer as teh default, use lp or lpr to print a file. No problem.
Comment 1 w unruh 2023-03-09 00:55:16 CET
Created attachment 13735 [details]
cups error.log file on local machine

Here is the error.log on the local machine. The item starting at 
08/Mar/2023:12:51:23 are when I asked chromium to print the displayed page to the remote printer.
to the remote printer.

The /etc/cups/printer.conf entry is

<DefaultPrinter HP311d>
PrinterId 7
UUID urn:uuid:1d5eca8b-d2b8-3f0f-72e7-4576a9344d29
AuthInfoRequired none
Info HP LaserJet 400 M401dne
Location Henn311
DeviceURI ipp://monopole:631/printers/Henn311-hp-duplex
State Idle
StateTime 1678312066
ConfigTime 1678234693
Type 6
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy retry-current-job
</DefaultPrinter>

As mentioned many other programs can print to this printer without trouble
Comment 2 sturmvogel 2023-03-09 00:56:02 CET
(In reply to w unruh from comment #0)
> Version-Release number of selected component (if
> applicable):cups-2.3.3op2-1.mga8  
> chromium-browser-108.0.5359.124-1.mga8

Would you mind to update your system properly and test again?

Actual cups-2.3.3op2-1.1.mga8.x86_64.rpm (you are one version behind!)
Actual chromium-browser-stable-110.0.5481.177-1.mga8.x86_64.rpm (you are 4 versions behind!)

You seem to not have you system updated for 3 month!
Comment 3 w unruh 2023-03-09 01:13:48 CET
No change.
chromium-browser-110.0.5481.177-1.mga8
cups-2.3.3op2-1.1.mga8
Same error message
Comment 4 Lewis Smith 2023-03-09 20:35:28 CET
It would be nice to have confirmation from anyone else using our chromium-browser[-stable], M8, remote printer; external Google offerings do not count.

CC'ing Christian for his opinion re the browser.
Also tv for his view re CUPS.

Source RPM: cups and chromium => chromium-browser-110.0.5481.177-1.mga8
CC: (none) => chb0, lewyssmith, thierry.vignaud

Comment 5 christian barranco 2023-03-14 20:06:54 CET
Hi. Without any guarantee, could you try out chromium-browser-stable-111.0.5563.64-2.mga8 in *tainted/updates_testing* ?
I have enforced the use_cups flag. It should be there by default, but Chromium code being a maze, I don't exclude other flags have turned it to false...
Comment 6 w unruh 2023-03-15 21:24:41 CET
It did not change anything. Ie, it still does not work.
Comment 7 katnatek 2023-03-16 03:59:35 CET
Running in terminal show something?
I remember a issue with printing and gtk applications

The solution that time was install gnome-keyring

And add the next to  ~/.profile

eval `/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh,gpg`
export SSH_AUTH_SOCK
export GPG_AGENT_INFO

Ho
Comment 8 katnatek 2023-03-16 04:00:53 CET
(In reply to katnatek from comment #7)
 
> Ho
That no is part of tip ;)
Comment 9 katnatek 2023-03-16 04:03:15 CET
Forget to say that after edit the ~/.profile file , is needed close and start the session again
Comment 10 w unruh 2023-03-16 05:44:50 CET
That would be strange since none of the printers use authentication, so it would be very strange that keyring would do anything.
Comment 11 katnatek 2023-03-16 17:53:56 CET
(In reply to w unruh from comment #10)
> That would be strange since none of the printers use authentication, so it
> would be very strange that keyring would do anything.

The printer i did have, neither, but time ago gtk apps produce a keyring error message and not print

BTW if run chrome/chromiun in terminal you see something when try to print?
Comment 12 katnatek 2023-03-16 18:58:19 CET
I found a interesting message in your log, No authentication data provided.
How you share the printer?

Take a look at this redhat bug that could help to bring some light 
https://bugzilla.redhat.com/show_bug.cgi?id=1793252
Comment 13 katnatek 2023-03-16 19:02:13 CET
Also in gentoo i found that could be chrome/chromium issue :(
https://forums.gentoo.org/viewtopic-p-8244370.html?sid=577e260309294c99bbef078287c2a246#8244370
Comment 14 w unruh 2023-03-16 20:33:54 CET
re comment 13, I am running 2.3.3op2 so the claim that 2.2.7 solves it either did not stick or is not relevant to my case.
Re comment 12, the symptoms are very different. It seems he could not print from anything to his samba printer. In my case everthing but chrome/chromium prints fine. 
So it seems definitely to be a chrome/chromium problem.
Comment 15 christian barranco 2023-03-17 07:58:13 CET
Hi. I found this below. How is the printer configured?
https://kb.printerlogic.com/s/article/Chromebook-printing-error-The-selected-printer-is-not-available-or-not-installed-correctly
Comment 16 w unruh 2023-03-17 17:07:50 CET
I looked at that. The problem is that if ipp were not set up on the print server, it would surely not work for any printing attempt. As stated printing works fine for firefox,okular, lp, lpr

Anyway, here is the current setup on the local machine

<DefaultPrinter HP311d>
PrinterId 7
UUID urn:uuid:1d5eca8b-d2b8-3f0f-72e7-4576a9344d29
Info HP LaserJet 400 M401dne
Location Henn311
DeviceURI ipp://monopole.physics.ubc.ca:631/printers/Henn311-hp-duplex
State Stopped
StateTime 1678911047
ConfigTime 1678234693
Reason paused
Type 6
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy retry-current-job
</DefaultPrinter>

and here is the setup on the remote print server


<DefaultPrinter Henn311-hp-duplex>
PrinterId 1
UUID urn:uuid:ecf3d1b9-0424-341d-4755-916a140e920e
Info Hewlett-Packard HP LaserJet 400 M401dne
Location monopole.physics.ubc.ca
MakeModel HP LaserJet 400 M401dne Postscript (recommended)
DeviceURI usb://HP/LaserJet%20400%20M401dne?serial=PHGFB73003
State Idle
StateTime 1678399210
ConfigTime 1533237015
Type 8425556
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy retry-job
Option fitplot true
</DefaultPrinter>


Note that this works for firefox, okular,lp, lpr on the local machine, just not for chrome or chromium.
Comment 17 Lewis Smith 2023-03-21 09:39:33 CET
(In reply to w unruh from comment #0)
> Description of problem:
> When trying to print a page on google-chrome or on chromium, I get a
> "Selected printer not available or not installed correctly" error message
> for some printers which are linked to a printer on another machine. In all
> cases, lpr, lp, xpdf, okular all print files without trouble.
Can you say whether this ever worked, or is a problem that has recently appeared?
Also, does printing from this browser work with a *local* printer?

Re comment 4, it is obvious now that we could use confirmation of this on a Cauldron/M9 system with:
chromium-browser[-stable], remote printer

(In reply to katnatek from comment #12)
> Take a look at this redhat bug that could help to bring some light 
> https://bugzilla.redhat.com/show_bug.cgi?id=1793252
That dates from 2020, and is generic rather than being chromium specific. Bill makes it clear that most printing to that printer does work.

(In reply to katnatek from comment #13)
> Also in gentoo i found that could be chrome/chromium issue :(
> https://forums.gentoo.org/viewtopic-p-8244370.
> html?sid=577e260309294c99bbef078287c2a246#8244370
And this from 2018, Chrome specific, with a further link:
 https://github.com/apple/cups/issues/5289
Is it possible that such a problem could persist for so long?

(In reply to christian barranco from comment #15)
> Hi. I found this below. How is the printer configured?
> https://kb.printerlogic.com/s/article/Chromebook-printing-error-The-selected-
> printer-is-not-available-or-not-installed-correctly
2021. It says specifically:
"Cause: IPP on printer is disabled.
Solution : Enable IPP printing on printer
But it looks from comment 16 that IPP is set: "DeviceURI ipp://..."
Comment 18 katnatek 2023-03-27 20:36:22 CEST
Could be some like https://bugs.mageia.org/show_bug.cgi?id=28758 ?
Comment 19 w unruh 2023-03-27 21:44:09 CEST
The problem is that This only affects some remote printers, and other printers work fine (I have about 5 different remote printers here) and some o f them work fine, and some of them do not work at all. 

This has certainly only started recently. It sounds suspiciously like a configuration problem, but I cannot for the life of me figure out what could be the problem. /var/log/cups/error_log contains no clue to me at least (or it is lost in the huge amount of stff generated in that log by the DEBUG facility that I have it running on).

What is so wierd is that this only is a problem on chrome/chromium amongst the many ways I can print (eg lpr, okular, firefox,....)

Again, the error message is
"The selected printer is not available or not installed correctly"

This only happens on some programs (chrome/chromium both) and for others they print without problems. And only happens for some, not all remote printers (usually the system has no attached printer). ,

It is a local problem and the error message comes up immediately, no wait so chromium/chrome is finding something wrong on the local machine, not the remote one.
Comment 20 w unruh 2023-03-27 22:08:15 CEST
OK in the error_log (I have the errors rinter onto a file /var/log/cups/error_log, so I can find them instead of trying to wade through the wasteland on sysemd journal.
Anyway, immediately after I try to print and get that error message about
"The selected printer not available or not installed correctly I get the following message in error_log. 
I have not set up authentication nor do I want it, nor have I set it up on the remote printer (under my control) 


D [27/Mar/2023:12:58:14 -0700] [Client 204] Waiting for request.
D [27/Mar/2023:12:58:14 -0700] [Client 204] GET /printers/hpd.ppd HTTP/1.1
D [27/Mar/2023:12:58:14 -0700] cupsdSetBusyState: newbusy="Active clients", busy="Active clients"
D [27/Mar/2023:12:58:14 -0700] [Client 204] Read: status=200, state=3
D [27/Mar/2023:12:58:14 -0700] [Client 204] No authentication data provided.
D [27/Mar/2023:12:58:14 -0700] [Client 204] Processing GET /printers/hpd.ppd
D [27/Mar/2023:12:58:14 -0700] [Client 204] cupsdSendHeader: code=404, type="text/html", auth_type=0
D [27/Mar/2023:12:58:14 -0700] [Client 204] Closing because Keep-Alive is disabled.
D [27/Mar/2023:12:58:14 -0700] [Client 204] Closing connection.
D [27/Mar/2023:12:58:14 -0700] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
Comment 21 Lewis Smith 2023-05-08 20:19:46 CEST
Sorry to have left you.

I think the last comment is what matters, /var/log/cups/error_log.

Assigning this to Thierry who looks after CUPS, hoping he will be able to shed some light.

Assignee: bugsquad => thierry.vignaud
CC: lewyssmith, thierry.vignaud => (none)


Note You need to log in before you can comment on or make changes to this bug.