Printer is not available in chromium snap

Thanks for the bug report, Heiko.

We do not have cups-control in Chromium. What is the output of 'snap connections chromium'? Is the cups one connected?

This is the output:

snap connections chromium
Schnittstelle Plug Slot Notizen
audio-playback chromium:audio-playback :audio-playback -
audio-record chromium:audio-record :audio-record -
bluez chromium:bluez :bluez -
browser-support chromium:browser-sandbox :browser-support -
camera chromium:camera :camera -
content chromium:foo-install-cups - -
content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 -
content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes -
content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes -
content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes -
cups chromium:cups cups:cups -
desktop chromium:desktop :desktop -
desktop-legacy chromium:desktop-legacy :desktop-legacy -
gsettings chromium:gsettings :gsettings -
home chromium:home :home -
joystick chromium:joystick :joystick -
mount-observe chromium:mount-observe - -
mpris - chromium:mpris -
network chromium:network :network -
network-bind chromium:network-bind :network-bind -
network-manager chromium:network-manager - -
opengl chromium:opengl :opengl -
password-manager-service chromium:password-manager-service - -
personal-files chromium:chromium-config :personal-files -
raw-usb chromium:raw-usb - -
removable-media chromium:removable-media :removable-media -
screen-inhibit-control chromium:screen-inhibit-control :screen-inhibit-control -
system-files chromium:etc-chromium-browser-policies :system-files -
system-packages-doc chromium:system-packages-doc :system-packages-doc -
u2f-devices chromium:u2f-devices :u2f-devices -
unity7 ...

It could be a problem in Chromium or Cups then.

If you start Chromium from the command line with

  chromium --enable-logging=stderr |& tee chromium.log

and work from there, do you see anything relevant in the output?

If yes, please attach the generated log file to this bug report.

Heiko, please run the following commands and post their output here:

    lpstat -v
    lpstat -p
    cups.lpstat -v
    cups.lpstat -p
    snap list | grep cups
    snap connections cups

I fixed the problem myself by setting the printer up with a cupsdriver. Since my printer is connected to my LAN as a networkprinter it is using the default "driverless" setup that works out of the box after i install Kubuntu. It works for native apps and flatpaks as well. Applications installed as snap seem to be unable to detect the printer. This happens on three different systems.

Heiko, even that you have found a workaround, could you continue help us what was going on? Could you follow the instructions of comment #4?

Here is the output as it is now after switching from driverless printing to a cups driver for my printer.

lpstat -v
Gerät für HP_Officejet_Pro_8610_2414BB: implicitclass://HP_Officejet_Pro_8610_2414BB/
Gerät für <email address hidden>: implicitclass://HP_Officejet_Pro_8610_2414BB%40HPFC3FDB2414BB.local/

lpstat -p
Drucker HP_Officejet_Pro_8610_2414BB ist im Leerlauf. Aktiviert seit Mo 03 Jul 2023 15:10:43 CEST
Drucker <email address hidden> ist im Leerlauf. Aktiviert seit Di 04 Jul 2023 16:40:45 CEST

cups.lpstat -v
device for HP_Officejet_Pro_8610_2414BB: proxy://%2Frun%2Fcups%2Fcups.sock/HP_Officejet_Pro_8610_2414BB
device for <email address hidden>: proxy://%2Frun%2Fcups%<email address hidden>

cups.lpstat -p
printer HP_Officejet_Pro_8610_2414BB is idle. enabled since Mon Jul 3 15:15:20 2023
printer <email address hidden> is idle. enabled since Tue Jul 4 16:40:45 2023

snap list | grep cups
cups 2.4.6-1 962 latest/stable openprinting** -

snap connections cups
Schnittstelle Plug Slot Notizen
avahi-control cups:avahi-control :avahi-control -
cups chromium:cups cups:cups -
cups-control - cups:cups-server -
cups-control cups:cups-control :cups-control -
home cups:home :home -
network cups:network :network -
network-bind cups:network-bind :network-bind -
network-manager-observe cups:network-manager-observe :network-manager-observe -
raw-usb cups:raw-usb :raw-usb -
system-files cups:etc-cups :system-files -

Hi,

I have the same issue. Heiko, your output is after you fixed the problem, right?

I just use my network printer on a fresh install and it shows up in the system printing dialog right away. It also shows up with lpstat. But inside Chromium snap it doesn't show up in the Chromium print dialog, and also when clicking "Use system printing dialog" I have the dialog, but no printer. Tbh, I have no idea about how the system printing works nowadays, because it used to run out of the box for a long time now :)

So, it seems there is something not in cups, but around it, that adds auto-detected?

Below are my outputs.

Best,
Stefan

❯ lpstat -v
device for HP_Color_LaserJet_MFP_M277dw_AF6996: implicitclass://HP_Color_LaserJet_MFP_M277dw_AF6996/

❯ lpstat -p
printer HP_Color_LaserJet_MFP_M277dw_AF6996 is idle. enabled since Sa 12 Aug 2023 08:24:00 CEST

❯ cups.lpstat -v
lpstat: No destinations added.

❯ cups.lpstat -p
lpstat: No destinations added.

❯ snap list | grep cups
cups 2.4.6-4 980 latest/stable openprinting** -

❯ snap connections cups
Interface Plug Slot Notes
avahi-control cups:avahi-control :avahi-control -
cups chromium:cups cups:cups -
cups-control - cups:cups-control -
cups-control cups:cups-host :cups-control -
home cups:home :home -
network cups:network :network -
network-bind cups:network-bind :network-bind -
network-manager-observe cups:network-manager-observe :network-manager-observe -
raw-usb cups:raw-usb :raw-usb -
system-files cups:etc-cups :system-files -

Hi,

I have the same issue as well, on two different boxes (ubuntu 22.04) with two different printers (HP & Samsung).

The printers show up in "system" settings. The Firefox snap is able to print correctly, it is connected to cups-control (not cups as the Chromium snap).

Here's the relevant outputs:

------------------------

user@box:~$ lpstat -v
device for HP_DeskJet_3630_series_91ACE7: implicitclass://HP_DeskJet_3630_series_91ACE7/
user@box:~$ lpstat -p
printer HP_DeskJet_3630_series_91ACE7 is idle. enabled since Tue 12 Sep 2023 09:50:24
user@box:~$ cups.lpstat -v
lpstat: No destinations added.
user@box:~$ cups.lpstat -p
lpstat: No destinations added.

user@box:~$ snap list | grep cups
cups 2.4.6-4 980 latest/stable openprinting** -

user@box:~$ snap connections cups
Interface Plug Slot Notes
avahi-control cups:avahi-control :avahi-control -
cups chromium:cups cups:cups -
cups-control - cups:cups-control -
cups-control cups:cups-host :cups-control -
home cups:home :home -
network cups:network :network -
network-bind cups:network-bind :network-bind -
network-manager-observe cups:network-manager-observe :network-manager-observe -
raw-usb cups:raw-usb :raw-usb -
system-files cups:etc-cups :system-files -

user@box:~$ snap connections chromium
Interface Plug Slot Notes
audio-playback chromium:audio-playback :audio-playback -
audio-record chromium:audio-record :audio-record -
bluez chromium:bluez :bluez -
browser-support chromium:browser-sandbox :browser-support -
camera chromium:camera :camera -
content chromium:foo-install-cups - -
content[gnome-42-2204] chromium:gnome-42-2204 gnome-42-2204:gnome-42-2204 -
content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes -
content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes -
content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes -
cups chromium:cups cups:cups -
desktop chromium:desktop :desktop -
desktop-legacy chromium:desktop-legacy :desktop-legacy -
gsettings...

I also tried restarting cups and the printer as suggested here https://forum.snapcraft.io/t/new-interface-cups-for-all-snaps-which-print/29702/5 but Chromium still does not show the printer queue as a Destination (only Save as PDF is available).

Changing the printerdriver from driverless to a selected Cups driver for the printermodell solved the issue on my end. It seems that snaps that are not using Cups-control are having trouble with connecting to printers using the driverless approach.