10

Please help me to confirm this is a browser problem!

I've posted the same problem in Google-Chrome Help because I suspect it is a browser-problem.

I'm using a HP Officejet Pro 9120e Series printer via WIFI on my Ubuntu 25.04 desktop. The printer is added via the Gnome Settings. Printing a test page and printing from Evince PDF-viewer and Chromium works fine. However printing from Google Chrome does not work. A peculiar thing is that some time after adding the printer a second printer automatically occurs (same name but with "Series" and some id-nr appended).

I've tried using both printer entries and found on Internet that Chrome has difficulties with driverless printers. Therefore I added a driver suited for some familiair printers from hplip (9010,9020,9110,9120,9130 Series). This works fine again from Evince but not from Google Chrome.

Update Meanwhile I've been investigating my problem further. I found https://wiki.ubuntu.com/DebuggingPrintingProblems very helpful in describing the diagnosis process.

Going through the steps I've diagnosed the following:

  • Most tests are successful as is to be expected because printing works OK mostly and only fails in Google Chrome.
  • List item Cupsctl sometimes returns "cupsctl: Connection lost"(freely translated from Dutch). It occurs directly after changing the
    LogLevel in cups. I presume cups is just restarted to make the debug effective!?
  • Using the troubleshooting Wizard in system-config-printer it 'hangs' undefinitely after pressing "Next/continue" (freely translated from Dutch) in a popup window that is blank (apart from the buttons). Should it contain a choice of printers to troubleshoot?

I've included the part of the cups error-log that contains a print from Chrome using the system-dialog-printwindow (ctrl-shift-P).

Further update: Because only Google-chrome seems to be malfunctioning I've tried comparing the debug-log from Google-chrome with the debug-log from Chromium (that functions OK). A noticeable difference is that where Chromium seems to go from spooling and sending the job tot the printer, Google chrome tries to 'stat' a non-existing file. I've included snapshots from both (please let me know if you require more context):

Latest update

I've completely removed Google-chrome using this excellent description in Ask Ubuntu and reinstalled it. However no change in the situation I suspect a bug in Google-chrome. Anyway I'm out of ideas!

I hope someone can help me and otherwise others searching for help in this matter will find the various methods of diagnosis I found helpful.

Tom
  • 103
  • 1
    Is there some common feature of the non-printing apps - for example, are they installed as snaps? – steeldriver Apr 22 '25 at 14:11
  • Same problem in MS Edge too. Firefox works OK though. – FedKad Apr 24 '25 at 17:48
  • I have the exact same problem on Ubuntu 25.04. Chromium and Firefox can print fine. – galatians May 06 '25 at 03:05
  • I see these 2 errors in the terminal running chrome:

    ERROR:components/device_event_log/device_event_log_impl.cc:202] [14:52:09.814] Printer: print_job_worker_oop.cc:133 Error initiating printing via service for document 10: kFailed

    [Error] [Frontend] Error in DBus call doListing: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying

     – galatians May 06 '25 at 19:55
  • @galatians I will try to post a bug report. It would be helpful if I could include your situation. Can you provide me with information on your configuration (Ubuntu version, Google Chrome version, printer etc.) and the relevant part of your (Chrome/system) log? – Tom May 07 '25 at 15:20

2 Answers2

7

This is a regression in Google Chrome that occurred on Feb 28th 2025 related to changing some UI components from GTK3 to GTK4. The bug and the regression are documented here: https://issues.chromium.org/issues/414635403

Fixes for the bug have been merged so I expect that a new release of Chrome will soon fix the problem. I expect that there is no real workaround other than to wait for the fixed build.

I noticed that my other laptop with Ubuntu 24.10 also has this problem but my 3rd laptop running Xubuntu 25.04 does not because Xubuntu still uses GTK3.

galatians
  • 449
  • 2
    The problem is fixed in a build 138.0.7170.0-1 of the branch 138. A stable release of this branch is planned to come available at Tue, Jun 24, 2025 (https://chromiumdash.appspot.com/schedule). – Tom May 25 '25 at 18:21
  • 1
    I've just updated to Google Chrome 138.0.7204.92 (Officiële build) (64-bits). The problem is solved! – Tom Jul 04 '25 at 15:21
0

I noticed the same problem printing to a Brother printer (MFC-J5855DW) on Google Chrome 136 & 137 (136.0.7103.92 & 137.0.7151.68) on Ubuntu 24.10 (GNOME 47) and Ubuntu 25.04 (GNOME 48). Printing to PDF still worked, however. Noticing that Chrome on my Chromebook still worked (Xubuntu 25.04 / Xfce 4.2), I installed and switched to Xfce in Ubuntu 24.10 and now I could print in Chrome 137. Alternatively, switching to the beta version of Chrome (138.0.7204.4) also allowed me to print in Chrome.

Hope this helps.

Additionally: Weirdly, while Chrome Beta prints, it only does so slowly and with the wrong settings (i.e., color when black & white is selected).

gmarquart
  • 1
  • Yes, Chrome 138 is fixed for me too but also prints really slow with the wrong color/monochrome setting. – galatians Jul 05 '25 at 17:21