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.
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.