[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-12-21 Thread Hywel Thomas
Hello all, I have been having the same problem (CUPS printer not showing/being available on Chromium), and seem to have fixed it as follows:- Open CUPS administration page (localhost:631/admin) under Server settings, enable 'Allow printing from the Internet' (I also have 'Allow remote

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-12-06 Thread Till Kamppeter
@wallento and @jose+ubu1, could you please run the command ps aux | grep cups-proxyd and post the output here and also could you attach the files /var/snap/cups/current/var/log/cups-proxyd_log /var/snap/cups/current/var/log/error_log /var/log/cups/error_log Attach the files one by one, in

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-09-12 Thread Heiko Gimbel
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. -- You received this bug notification because

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-09-11 Thread joseguzman
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). -- You received this bug notification because you

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-09-11 Thread joseguzman
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

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-07-04 Thread Heiko Gimbel
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 HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local:

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-07-03 Thread Till Kamppeter
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? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu.

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-07-03 Thread Heiko Gimbel
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

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-07-03 Thread Till Kamppeter
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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-07-03 Thread Till Kamppeter
** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu.

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-07-03 Thread Nathan Teodosio
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. ** Changed