Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#54748 - [chromium] printing does not work, printer is visible but no job was send to the printer
Attached to Project:
Arch Linux
Opened by Christian Rebischke (Shibumi) - Sunday, 09 July 2017, 20:03 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 22 July 2017, 14:47 GMT
Opened by Christian Rebischke (Shibumi) - Sunday, 09 July 2017, 20:03 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 22 July 2017, 14:47 GMT
|
DetailsHello,
I have problems with chromium and printing. When I print over cups directly via `lpr` commandline it works, but the print-dialog in chromium does not work anymore since the last upgrade. The printer is visible, but when I click on 'print' there is no job in the queue of cups. Does this have something todo with the new 'native printer support' in chromium 59? |
This task depends upon
https://www.reddit.com/r/chrome/comments/6lmmk1/printing_from_browser_stopped_working_linux/
except that I can see the printer at least.
Not sure about not being able to print using Chromium's built-in print dialog. I printed a document on June 29th with no issues and also tested now that it's able to submit a print job (didn't turn on the printer to actually print it though).
Check if the following works:
1) Printing from Chromium using the system dialog (Ctrl+Shift+P)
2) Printing from other GTK3 applications
3) If everything fails, visit http://localhost:631/ and confirm that no print job was submitted
Assuming the issue is reproducible in Chrome as well, you could try reporting it upstream at https://bugs.chromium.org/p/chromium/issues/list (without further logs and repro steps, they might just say "works for me" though)