Addendum: I've had another closer look at the temporary queues code and upstream discussions and I seem to have neglected the most significant configuration for mr6.1. Namely "without cups-browsed or manual config". This in fact works now because libgtk specifically doesn't try to just send garbage to the printer anymore but actually does it via cups by creating a temporary printer which gets removed after some inactivity.
The queue creation seems to be inhibited only if a manually added printer of just the right name already exists. On Sat, Feb 26, 2022 at 07:43:10PM +0100, Daniel Gröber wrote: > Here are my test results: > With mr6.1 and cups-browsed auto-detection: > > Brother_HL_L5100DN_series (works) > > With mr6.1, cups manual config and default name[1]: > > Brother_HL-L5100DN_series_ (works) > Brother_HL_L5100DN_series (Status: Rejecting jobs, won't print) > > With mr6.1, cups manual config and corrected name[1]: > > Note: Here we use all underscores in the configured printer name to > make the merging logic trigger. > > Brother_HL_L5100DN_series (works) > > With mr6.1, both cups manual and cups-browsed auto-config and corrected > name[1] > > Brother_HL_L5100DN_series (cups manual, works) > Brother_HL_L5100DN_series@brother-hl-l5100dn.local (cups-browsed, > works) With mr6.1, cups installed, no cups-browsed, no manual config: Brother_HL_L5100DN_series (cups temporary queue, works) I'm also not sure what was up with the (manual+default name) configuration. I tried again and now the libgtk temporary queue entry prints just fine too: With mr6.1, cups manual config and default name[1]: Brother_HL-L5100DN_series_ (works) Brother_HL_L5100DN_series (works) I was able to reproduce the "Rejecting Jobs" outcome a couple of times, but not reliably. Together with picking the right printer name I was once able to get into a state where the rejecting print entry is the only one (: Trying to resume the temporary queue in the cups web interface also didn't help with that. So there is still some potential for improvement here but I agree mr6.1 is the way to go if we want printing to work in more cases than currently. --Daniel
signature.asc
Description: PGP signature